Read the docs

Prompt injection in Vikunja veans via project and task metadata

Priority LOW 10CWE-1427Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Passive
Attack complexity
High
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Vikunja veans before 2.7.1 contains a prompt injection flaw (CWE-1427) that lets project members with write access inject instructions through project titles or task content. The content is rendered verbatim inside the coding agent's instruction block, and the prime hook loads it on SessionStart and PreCompact. An attacker who has write access can therefore cause the agent to modify the developer's checkout or run commands.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

Description from the CNA

Vikunja veans before 2.7.1 contains a prompt injection vulnerability that allows project members with write access to inject instructions by setting project titles or task content rendered verbatim inside the coding agent's authoritative instruction block. Attackers can craft ProjectTitle or task descriptions that the prime hook loads on SessionStart and PreCompact, causing the agent to modify the developer's checkout or run commands.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00154 4th percentileScored 2026-11-16
Fix Fixed vikunja (go-vikunja): 2.7.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
go-vikunjavikunjabefore 2.7.12.7.1Patch availableCNA
  • vikunja Vendorgo-vikunja Affected before 2.7.1 Fixed in 2.7.1 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:*——go-vikunja
  • cpe:2.3:a:vikunja:vikunja:*:*:*:*:*:*:*:* Versions — — ·go-vikunja

Remediation

Update go-vikunja vikunja to version 2.7.1, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

  • Fix · CNA vikunja (go-vikunja) Fixed in 2.7.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    go-vikunja vikunja 2.7.1

    39 records Highest priority Priority HIGH 2 HIGH, 7 MEDIUM, 30 LOW

    Other records, highest priority first

    • TI-2026-86673 Uncontrolled resource consumption in Vikunja lets users bypass pagination limitsPriority HIGH 73
    • TI-2026-86670 Insufficient session expiration in Vikunja lets revoked tokens authenticatePriority HIGH 68
    • TI-2026-86666 Information disclosure in Vikunja webhook related_tasks payloadPriority MEDIUM 64

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-123498
  2. 2026-11-08 Alias added: GHSA-3v4w-4754-gmfj
  3. 2026-11-09 CISA SSVC decision points changed

References

  • TI-2026-40929 Authorization bypass in go-vikunja Vikunja CVSS 4.0CRITICAL 9.3
  • TI-2026-21967 Vijkunja has Weak Password Policy Combined with Persistent Sessions After Password Change CVSS 3.1CRITICAL 9.1
  • TI-2026-62115 Vikunja before 2.6.0 Privilege Escalation via Link Share Hash CVSS 4.0HIGH 8.7
  • TI-2026-62108 Vikunja before 2.6.0 Authentication Bypass via CalDAV BasicAuth CVSS 4.0HIGH 8.7
  • TI-2026-62107 Vikunja before 2.6.0 Authentication Bypass via Unthrottled API CVSS 4.0HIGH 8.7
  • TI-2026-26971 Vikunja ahs a TOTP Two-Factor Authentication Bypass via OIDC Login Path CVSS 3.1CRITICAL 9.1
See all 105 →

Sources