VulnerabilityPublished 8 Nov 2026

CVE-2026-123495: vikunja · Cross-Site Request Forgery (CSRF)

Affects vikunjaSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.1 Medium : upgrade to 2.7.1 when convenient.

Data as of 8 Nov 2026, 02:32 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (VulnCheck)	CVSS 4.0	5.1
CNA (VulnCheck)	CVSS 3.1	4.6

Patch: Available – fixed in 2.7.1

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade vikunja to 2.7.1.

Affected software

Product	Affected	Fixed in
go-vikunjavikunja	Affected >=2.0.0 <2.7.1	Fixed in 2.7.1
Govikunja`pkg:golang/vikunja`Other threats	Affected >=2.0.0 <2.7.1	Fixed in 2.7.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Vikunja to version 2.7.1 or later, where this CSRF vulnerability has been fixed. No other mitigations are specified or required once the official fix is applied.

Description

Vikunja versions 2.0.0 up to but not including 2.7.1 are vulnerable to a Cross-Site Request Forgery (CSRF) attack on the /api/v2 login and OIDC callback endpoints. These endpoints accept form-encoded bodies without verifying CSRF tokens or Origin headers, allowing an attacker with an account to trick a victim into switching to the attacker's account. This can expose data the victim subsequently adds. The vulnerability is fixed in version 2.7.1.

Impact

An attacker with an existing account can exploit this vulnerability to cause a victim to unknowingly switch to the attacker's account, potentially exposing data that the victim adds after the switch. This undermines user session integrity and can lead to unauthorized data exposure. The CVSS 4.0 score is 5.1 (medium severity), reflecting network attack vector, low complexity, and user interaction required.

Summary

Vikunja before version 2.7.1 improperly handles form-encoded requests on its login and OIDC callback API endpoints by not enforcing CSRF or Origin checks. This allows an authenticated attacker to craft a page that causes a victim to submit the attacker's credentials or OIDC code, effectively switching the victim's session to the attacker's account. This login CSRF vulnerability can lead to data exposure where the victim unknowingly adds data to the attacker's account. The issue is resolved in Vikunja 2.7.1.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Nov 2026, 02:32 UTC

Technical details

References

Community reviews

Related threats