Go Vikunja API file read and privilege escalation via XML binding
Affects Vikunja 0.14.0 through 2.7.1 where XML request bodies reach the v1 API. Fixed in 2.8.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.8.0
- Who is exposed
- Specific setups only
Summary
Written by a model
Vikunja from 0.14.0 before 2.8.0 contains a mass assignment vulnerability that allows authenticated users to set json-hidden fields by sending XML request bodies to the v1 API. Attackers can set BackgroundFileID on project creation to download any stored file via the background endpoint, or create bots with IsAdmin set to gain instance-admin access.
Who should check
Teams running Vikunja 0.14.0 through 2.7.1 with the v1 API exposed; instances with the admin_panel license feature face instance-admin escalation.
“Affecting vikunja >= 0.14.0, < 2.8.0”
What to do
Check whether your setup matches what the bug needs.
Vikunja versions 0.14.0 through 2.7.1 (fixed in 2.8.0) XML request bodies must reach the v1 API; the v2 API rejects XML Privilege escalation via bots only works where the admin_panel license feature is enabledUpgrade to a fixed version: 2.8.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-134282 (Vikunja 0.14.0 before 2.8.0 Arbitrary File Read and Privilege Escalation via XML Binding), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-134282 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 0.14.0, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Vikunja versions 0.14.0 through 2.7.1 (fixed in 2.8.0) (source: https://www.vulncheck.com/advisories/vikunja-0.14.0-before-2.8.0-arbitrary-file-read-and-privilege-escalation-via-xml-binding)
- XML request bodies must reach the v1 API; the v2 API rejects XML (source: https://www.vulncheck.com/advisories/vikunja-0.14.0-before-2.8.0-arbitrary-file-read-and-privilege-escalation-via-xml-binding)
- Privilege escalation via bots only works where the admin_panel license feature is enabled (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-fppf-ghrf-8wp7)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134282 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134282 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-fppf-ghrf-8wp7
- https://www.vulncheck.com/advisories/vikunja-0.14.0-before-2.8.0-arbitrary-file-read-and-privilege-escalation-via-xml-binding
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-134282
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-134282"}.Affected versions
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 34 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · go-vikunja/vikunja · Advisory GHSA-fppf-ghrf-8wp7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134282 |
| Record | NVD · CVE-2026-134282 |
| Other links 1 | |
| Link | vulncheck.com · advisories/vikunja-0.14.0-before-2.8.0-arbitrary-file-read-and-privilege-escalation-via-xml-binding |
Questions about CVE-2026-134282
Is CVE-2026-134282 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: cve.now feed data
What does this mean?
Authenticated non-admin users can read any stored file on the instance, including other users' attachments, avatars and data exports. Where the admin_panel feature is enabled, they can also gain instance-admin access by creating an admin-flagged bot.
Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-134282?
code.vikunja.io/api (Go): from 0.14.0 before 2.8.0.
Source: cve.now feed data
Am I affected, and how do I check?
The range is Vikunja 0.14.0 up to 2.7.1. The file read needs XML request bodies to reach the v1 API, since the v2 API rejects XML. The bot-based privilege escalation only works where the admin_panel license feature is enabled, so check the installed Vikunja version against that range and whether that feature is enabled.
Source: vulncheck.com, github.com
How do I fix CVE-2026-134282?
Upgrade to Vikunja 2.8.0 or later, which is the fixed version in the affected range.
Source: vulncheck.com, github.com
Related
- CVE-2026-123531Vikunja 1.0.0 before 2.7.1 Pagination Limit Bypass via page=0 Parameter
- CVE-2026-134284Vikunja from 1.0.0 before 2.8.0 Account Takeover via OIDC Email Fallback
- CVE-2026-123528Vikunja before 2.7.1 Insufficient Session Expiration via HTTP Token Middleware
- CVE-2026-134265Vikunja 2.4.0 before 2.8.0 Denial of Service via Unbounded Table Rowspan/Colspan
- CVE-2026-134266Vikunja 0.19.0 before 2.8.0 Denial of Service via Datemath Business-Day Filter
- CVE-2026-134268Vikunja 0.21.0 before 2.8.0 Denial of Service via Project Position Recalculation
No corrections so far. Something wrong on this page? Report an error.