CVE-2026-123508: Vikunja before 2.7.1 Supply Chain Risk via Unpinned xgo Release Toolchain
Noroxi assessment
Priority: Monitor (action score 8/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.09% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. Administrator privileges are required. Special conditions such as timing or configuration are required.
- Fixed version: go-vikunja vikunja 2.7.1.
Low priority for now. Upgrade to go-vikunja vikunja 2.7.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 8, 2026
- Updated
- Nov 8, 2026
- EPSS
- 0.0% · 0th percentile
- CWE
- CWE-494
Report tools
Action score
8
Monitor
Low priority for now.
- CVSS
- 8 / 40 · 2.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.0%
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 2.0
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
go-vikunja vikunja
- 2.7.1not affected
- before 2.7.1affected · semver
Same product
go-vikunja: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-68582Vikunja 0.24.0 Broken Object Level Authorization via Link-Share Token37Monitor
- CVE-2026-123531Vikunja 1.0.0 before 2.7.1 Pagination Limit Bypass via page=0 Parameter34Monitor
- CVE-2026-91985Vikunja before 2.6.0 Privilege Escalation via Link Share Hash34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-123506Nov 8, 2026 · Vikunja 2.2.0 before 2.7.1 Token Scope Bypass via Project Webhook Endpoints21Monitor
- ← EarlierCVE-2026-123507Nov 8, 2026 · Vikunja 0.24.0 before 2.7.1 Denial of Service via Nil Bucket Filter20Monitor
- Later →CVE-2026-123509Nov 8, 2026 · Vikunja before 2.7.1 Denial of Service via Unbounded Kanban Bucket Count21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| go-vikunja vikunja | 2.7.1 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 9, 2026+2 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- Administrator privileges are required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- High
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-494 · Download of Code Without Integrity CheckCVSS 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/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
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Software Integrity AttackCAPEC-184Low
- Malicious Software DownloadCAPEC-185Very High
- Malicious Software UpdateCAPEC-186High
- Malicious Automated Software Update via RedirectionCAPEC-187likelihood: High · High
- Malicious Manual Software UpdateCAPEC-533likelihood: Low · High
- Open-Source Library ManipulationCAPEC-538likelihood: Low · High
- Malicious Automated Software Update via SpoofingCAPEC-657likelihood: High · High
- Adversary in the Browser (AiTB)CAPEC-662likelihood: High · Very High
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.