Go Vikunja API email disclosure in project link share list
Only affects Vikunja 0.9.0 through 2.7.1, and only on projects where another user has created a link share. 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.9.0 before 2.8.0 contains an information disclosure vulnerability that allows project admins to view share creators' email addresses via the link share list endpoint. Attackers with admin permission can request the project shares endpoint and read the shared_by email field, exposing addresses of creators including former project members.
Who should check
Teams running Vikunja 0.9.0 through 2.7.1 (Go module code.vikunja.io/api) that use project link shares, especially project admins.
“Since v0.9.0, when ReadAll started populating SharedBy , up to and including v2.7.1.”
What to do
Check whether your setup matches what the bug needs.
Vikunja versions 0.9.0 through 2.7.1 are affected; fixed in 2.8.0. Another user must already have created a link share on the project. The attacker must hold admin permission on the project.Upgrade 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-134272 (Vikunja 0.9.0 before 2.8.0 Email Disclosure via Project Link Share List), 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-134272 (entry last updated 2026-11-21):
Affected:
- Go package code.vikunja.io/api: from 0.9.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.9.0 through 2.7.1 are affected; fixed in 2.8.0. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8g2q-76h7-8fh7)
- Another user must already have created a link share on the project. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8g2q-76h7-8fh7)
- The attacker must hold admin permission on the project. (source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8g2q-76h7-8fh7)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-134272 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134272 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-8g2q-76h7-8fh7
- https://www.vulncheck.com/advisories/vikunja-0.9.0-before-2.8.0-email-disclosure-via-project-link-share-list
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-134272
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-134272"}.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
- Severity5.1/10CVSS 5.1
- No patch0/5No signal
What would change the score
- Would score about 73 if added to CISA KEV
- Would score about 68 if CISA's SSVC rates exploitation active
- Would score about 30 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-8g2q-76h7-8fh7 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-134272 |
| Record | NVD · CVE-2026-134272 |
| Other links 1 | |
| Link | vulncheck.com · advisories/vikunja-0.9.0-before-2.8.0-email-disclosure-via-project-link-share-list |
Questions about CVE-2026-134272
Is CVE-2026-134272 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 project admin can learn the email addresses of every user who created a link share on that project, including former members.
Source: github.com
Which versions are affected by CVE-2026-134272?
code.vikunja.io/api (Go): from 0.9.0 before 2.8.0.
Source: cve.now feed data
Am I affected, and how do I check?
Vikunja versions 0.9.0 up to and including 2.7.1 are affected. The issue needs a link share created by another user to already exist on the project, and the attacker must hold admin permission on that project. To check, look at the installed Vikunja version.
Source: github.com
How do I fix CVE-2026-134272?
Upgrade Vikunja to 2.8.0 or later, which is the fixed version named in the advisory.
Source: github.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.