Go Vikunja API denial of service in Planka migration converter
- Exploited
- No known exploitation
- Fix
- Fixed in 2.8.0
- Who is exposed
- Specific setups only
Summary
Vikunja from 2.6.0 before 2.8.0 contains a resource exhaustion vulnerability in the Planka migration converter that multiplies task allocations for duplicate list IDs. Attackers controlling a Planka server can return boards with duplicate list IDs and many cards to exhaust memory and OOM-kill the Vikunja process.
Who should check
Teams running self-hosted Vikunja 2.6.0 through 2.7.1 that use the Planka migration import, or anyone embedding go-vikunja code.topbar api module
“Vikunja from 2.6.0 before 2.8.0 contains a resource exhaustion vulnerability in the Planka migration converter”
What to do
Check whether your setup matches what the bug needs.
Vikunja versions 2.6.0 up to but not including 2.8.0 (affected range per GitHub: 2.6.0 through 2.7.1) The Planka migration import feature must be used The Planka server being migrated from must return boards with duplicate list IDs and many cardsUpgrade 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-134273 (Vikunja from 2.6.0 before 2.8.0 Denial of Service via Planka Migration), 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-134273 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 2.6.0, fixed in 2.8.0
Fixed versions: 2.8.0.
Conditions (all must be true for the bug to be hit):
- Vikunja versions 2.6.0 up to but not including 2.8.0 (affected range per GitHub: 2.6.0 through 2.7.1) (source: https://www.vulncheck.com/advisories/vikunja-from-2.6.0-before-2.8.0-denial-of-service-via-planka-migration)
- The Planka migration import feature must be used (source: https://www.vulncheck.com/advisories/vikunja-from-2.6.0-before-2.8.0-denial-of-service-via-planka-migration)
- The Planka server being migrated from must return boards with duplicate list IDs and many cards (source: https://www.vulncheck.com/advisories/vikunja-from-2.6.0-before-2.8.0-denial-of-service-via-planka-migration)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-134273 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134273 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-q472-pmpr-4h46
- https://www.vulncheck.com/advisories/vikunja-from-2.6.0-before-2.8.0-denial-of-service-via-planka-migration
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-134273
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-134273"}.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
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 32 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-q472-pmpr-4h46 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134273 |
| Record | NVD · CVE-2026-134273 |
| Other links 1 | |
| Link | vulncheck.com · advisories/vikunja-from-2.6.0-before-2.8.0-denial-of-service-via-planka-migration |
Questions about CVE-2026-134273
Is CVE-2026-134273 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?
A Planka migration converter in Vikunja multiplies task allocations when a Planka board has duplicate list IDs. A malicious Planka server can return such boards with many cards, which can exhaust server memory and cause the Vikunja process to be killed by the out-of-memory handler, a denial of service.
Source: vulncheck.com
Which versions are affected by CVE-2026-134273?
code.vikunja.io/api (Go): from 2.6.0 before 2.8.0.
Source: cve.now feed data
Am I affected, and how do I check?
Vikunja versions from 2.6.0 up to but not including 2.8.0 are affected, and GitHub lists the affected range as 2.6.0 through 2.7.1. Only installations that use the Planka migration import feature are in scope. To check the version, look at the Vikunja version reported by the server or the release tag in use.
Source: vulncheck.com
How do I fix CVE-2026-134273?
Upgrade Vikunja to version 2.8.0 or later, which is the fixed version.
Source: vulncheck.com
Related
- CVE-2026-123531Vikunja 1.0.0 before 2.7.1 Pagination Limit Bypass via page=0 Parameter
- CVE-2026-134282Vikunja 0.14.0 before 2.8.0 Arbitrary File Read and Privilege Escalation via XML Binding
- 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
No corrections so far. Something wrong on this page? Report an error.