Read the docs

Protocol downgrade in veans server discovery exposes Vikunja traffic

Priority LOW 34CWE-319Published · Updated

Key facts

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

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-319.

Summary

Vikunja veans before 2.7.1 contains a protocol downgrade flaw in serverCandidates, classified as cleartext transmission of sensitive information (CWE-319). An on-path attacker who blocks HTTPS ports can force the client onto plain HTTP during veans init and login, because discovery accepts an unverified HTTP response. The attacker can capture passwords, TOTP codes and bot tokens and keep reading cleartext API traffic.

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 protocol downgrade vulnerability in serverCandidates that allows on-path attackers to force plain HTTP during veans init and login. Attackers can block HTTPS ports so discovery accepts an unverified HTTP response, capturing passwords, TOTP codes or bot tokens and persisting cleartext API traffic.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00158 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
Total

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

Upgrade vikunja veans to version 2.7.1 or later.

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-123497
  2. 2026-11-08 Alias added: GHSA-rg35-8p7r-mq2v
  3. 2026-11-09 Priority changed: MEDIUM → LOW
  4. 2026-11-10 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