CVE-2026-123527

Vikunja 2.4.0 before 2.7.1 API Token Scope Collision Authorization Bypass

CVSS score

5.3

EPSS probability

—

Risk score

0.5

Published

8 h ago

Overview Public Exploits (0)Newsroom Vulnerability Timeline

Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

DayBreach AI Explanation

Verified against sources

Vikunja API Token Scope Collision Authorization Bypass (CVE-2026-123527)

Sources read

Source agreement

0/2

Evidence confidence

%44

Short explanation

Vikunja 2.4.0‑2.7.1 suffers an authorization bypass due to v1/v2 API token permission key collisions; limited‑scope tokens can perform unintended delete and update actions.

Why does it matter?

Unauthorized token holders can delete or modify data, creating integrity and confidentiality risks.

What should be done?

Monitor token usage and scopes
Revoke unnecessary tokens and rotate them
Upgrade to version 2.7.1 or later per vendor guidance
Track official advisories since patch status is unknown
Strengthen access controls and auditing

Note on uncertainty

2 alanda kaynak uyuşmazlığı var. DayBreach bu değerleri saklamadı; kaynak karşılaştırması aşağıda gösteriliyor.

Chain of evidence and sources3 verified claims

CVE-2026-123527, Vikunja 2.4.0‑2.7.1 sürümlerinde API token kapsam çakışması nedeniyle yetkilendirme bypass oluşturur.

S0 · daybreach-canonical S1 · cvelist S2 · nvd

Sınırlı kapsamlı tokenlar, proje arka planlarını silebilir ve bucket oluşturma‑sadece tokenları mevcut bucket’ları güncelleyebilir.

S0 · daybreach-canonical

Resmî kaynaklarda yama durumu doğrulanamadı; durum UNKNOWN olarak rapor edilmiştir.

S0 · daybreach-canonical

Show the technical text from the sources

Vikunja from 2.4.0 before 2.7.1 contains an authorization bypass vulnerability that allows token holders to perform unintended operations due to colliding v1 and v2 API token permission keys. Attackers with a token scoped to read project backgrounds can delete them via the v2 DELETE background route, and bucket create-only tokens can update existing buckets.

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

CWE: CWE-863

This explanation was compiled automatically from the source records. Scores, active exploitation, patch and exploit status come straight from the sources.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-123527 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

ID	VENDOR	PRODUCT	ACTION
1	go-vikunja	vikunja	View

Total affected vendors: 1|Products: 1

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCORE	VERSION	SEVERITY	VECTOR	SOURCE
5.4	CVSS V3_1	MEDIUM	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L	CVE CNA
5.4	CVSS V31	MEDIUM	CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L	NVD
5.3	CVSS V4_0	MEDIUM	CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N	CVE CNA
5.3	CVSS V40	MEDIUM	CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X	NVD

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.

Restrict access to internet-facing services and apply network segmentation.

Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.

Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-123527 is associated with the following CWEs:

CWE-863: Common Weakness Enumeration Entry CWE-863

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-123527 weaknesses.

CAPEC-66: SQL Injection CAPEC-126: Path Traversal CAPEC-28: OS Command Injection

Attack Vector and Accessibility

ExposureAğ üzerinden

PermissionsLow

UserGerekmiyor

Official Sources and Advisories

GitHub Security Advisory (GHSA-j5v7-qcwp-5g32)vendor-advisory VulnCheck Advisory: Vikunja 2.4.0 before 2.7.1 API Token Scope Collision Authorization Bypassvendor-advisory

CVSS Vector Radar Chart

5.3 / 10

Vulnerability Scoring Details

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

Attack VectorNetwork

Attack ComplexityLow

Privileges RequiredLow privileges

User InteractionNone required

Confidentiality (Gizlilik)Low

Integrity (Bütünlük)None

Availability (Erişilebilirlik)Low

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

go-vikunja

Weakness Type (CWE & CAPEC)

CWE-863

Similar Vulnerabilities

8.7

CVE-2026-123531Vikunja 1.0.0 before 2.7.1 Pagination Limit Bypass via page=0 Parameter

Vendorgo-vikunja Productvikunja

Patch status unknown8 h ago

8.4

CVE-2026-123512Vikunja before 2.7.1 Sensitive Token Exposure via URL Query in Access Logs

Vendorgo-vikunja Productvikunja

Patch status unknown8 h ago

7.6

CVE-2026-123528Vikunja before 2.7.1 Insufficient Session Expiration via HTTP Token Middleware

Vendorgo-vikunja Productvikunja

Patch status unknown8 h ago

7.6

CVE-2026-123513Vikunja before 2.7.1 Auth Token Leak via API URL Change

Vendorgo-vikunja Productvikunja

Patch status unknown8 h ago

7.6

CVE-2026-123497Vikunja veans before 2.7.1 HTTPS to HTTP Downgrade in Server Discovery

Vendorgo-vikunja Productvikunja

Patch status unknown8 h ago

7.1

CVE-2026-123525Vikunja before 2.7.1 Memory Exhaustion DoS via Trello, Todoist and Microsoft To Do Migrations

Vendorgo-vikunja Productvikunja

Patch status unknown8 h ago

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

Get a free key Documentation

curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-123527"

Vikunja 2.4.0 before 2.7.1 API Token Scope Collision Authorization Bypass

Impact on My Inventory

Vulnerability description

DayBreach AI Explanation

Short explanation

What should be done?

IMPACT: Affected Products and Software

Affected Products

RED HAT CSAF/VEX: Product Impact Check

SCORING: CVSS from Multiple Sources

CVSS Scores

Patch and Remediation Guide

Solution & Remediation Advisory

Public exploit and active exploitation status

Verified exploit intelligence

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

Common Attack Pattern Enumeration and Classification (CAPEC)

Attack Vector and Accessibility

Official Sources and Advisories

CVSS Vector Radar Chart

Vulnerability Scoring Details

Weakness Type (CWE & CAPEC)

Similar Vulnerabilities

Get this vulnerability through the API

DayBreach

Glossary & Reference

Directories & Feeds

RSS & Integration