CVE-2026-123499 json
Vikunja veans before 2.7.1 Credential Leak via Repo-Controlled .veans.yml Server
published 21d ago modified yesterday also EUVD-2026-119384 , GHSA-3rrq-h284-5vpx
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository go-vikunja/vikunja. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
Vikunja veans before 2.7.1 contains a credential exposure vulnerability that allows malicious repository authors to capture API tokens by specifying an attacker-controlled server in .veans.yml. When veans runs in an untrusted checkout, it sends VEANS_TOKEN as a Bearer token, or login passwords, TOTP codes and tokens, to that server, granting attackers the victim's Vikunja access.
Patch / fix
- go-vikunja vikunja 2.7.1
Is CVE-2026-123499 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.11% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.0 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:L/A:N |
| CNA | 4.0 | 6.0 | CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
Affected products
- go-vikunja vikunja
Classification
- Weakness
-
- CWE-346 Origin Validation Error
References
-
github.com
/go-vikunja/vikunja/security/advisories/GHSA-3rrq-h284-5vpx
vendor-advisory, advisory
-
vulncheck.com
/advisories/vikunja-veans-before-2.7.1-credential-leak-via-repo-controlled-veans-yml-server
third-party-advisory
Sources
- CVE List CVE-2026-123499
- NVD CVE-2026-123499
- Maintainer advisory GHSA-3rrq-h284-5vpx
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of go-vikunja/vikunja published their own advisory on GitHub. Reviewed sources take precedence over it.