CVE-2026-68581

HIGHPre-NVD 8.18.1—
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-02. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Vikunja versions 0.22.0 through 2.3.0 fail to validate the principal type in API token management. Because user IDs and link-share IDs are independent numeric sequences and both resolve through a generic web.Auth.GetID() interface, a link-share JWT whose numeric ID equals a target user's ID is treated as that user by the /api/v1/tokens endpoints. An authenticated attacker can obtain a target's numeric user ID via authenticated user search, then create link shares on an attacker-writable project until the link-share sequence reaches that value, and use the resulting link-share JWT to list, create, and delete the target user's API tokens (including issuing a new token with attacker-chosen scopes under the target's permissions). Fixed in version 2.4.0.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
52(Track*)
EG Risk 52/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

August 2, 2026

Last Modified

August 3, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
generic Patch Available

Vikunja 0.22.0 through 2.3.0 Authentication Bypass via Principal ID Collision | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vikunja-through-authentication-bypass-via-principal-id-collision
github_commit

commit 95b7e673fb5e (go-vikunja/vikunja)

Fix landed in go-vikunja/vikunja commit 95b7e673fb5e — awaiting tagged release

https://github.com/go-vikunja/vikunja/commit/95b7e673fb5ee407498fa4b13e8b4c57847a4a0b
github_commit

commit e6b25bd57b53 (go-vikunja/vikunja)

Fix landed in go-vikunja/vikunja commit e6b25bd57b53 — awaiting tagged release

https://github.com/go-vikunja/vikunja/commit/e6b25bd57b537ef9a72b5acdadf446ca5ef77bfa
github Patch Available🟡 PoC Available

Link-share principal ID collision allows cross-account API token issuance and management · Advisory · go-vikunja/vikunja · GitHub

https://github.com/go-vikunja/vikunja/security/advisories/GHSA-vvcv-vpph-h844

Vendor Advisories for CVE-2026-68581(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 77× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-20 22:56 UTCEPSS rescore
  2. 2026-08-20 20:33 UTCGHSA enrichment
  3. 2026-08-20 07:47 UTCGHSA enrichment
  4. 2026-08-19 19:01 UTCEG score recompute
  5. 2026-08-19 19:01 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 04:36 UTCGHSA enrichment
  8. 2026-08-18 15:50 UTCEG score recompute
  9. 2026-08-18 15:50 UTCGHSA enrichment
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 01:24 UTCEG score recompute
  13. 2026-08-18 01:24 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 12:38 UTCGHSA enrichment
  16. 2026-08-16 23:52 UTCEG score recompute
  17. 2026-08-16 23:52 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 11:06 UTCEG score recompute
  21. 2026-08-16 11:06 UTCGHSA enrichment
  22. 2026-08-15 22:20 UTCGHSA enrichment
  23. 2026-08-15 09:34 UTCEG score recompute
  24. 2026-08-15 09:34 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 52 more
  1. 2026-08-14 20:47 UTCGHSA enrichment
  2. 2026-08-14 08:01 UTCEG score recompute
  3. 2026-08-14 08:01 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 19:15 UTCGHSA enrichment
  6. 2026-08-13 06:29 UTCGHSA enrichment
  7. 2026-08-12 17:42 UTCEG score recompute
  8. 2026-08-12 17:42 UTCGHSA enrichment
  9. 2026-08-12 13:51 UTCEPSS rescore
  10. 2026-08-12 04:56 UTCGHSA enrichment
  11. 2026-08-11 16:10 UTCEG score recompute
  12. 2026-08-11 16:10 UTCGHSA enrichment
  13. 2026-08-11 03:24 UTCEG score recompute
  14. 2026-08-11 03:24 UTCGHSA enrichment
  15. 2026-08-11 00:00 UTCEPSS rescore
  16. 2026-08-10 14:38 UTCGHSA enrichment
  17. 2026-08-10 01:52 UTCEG score recompute
  18. 2026-08-10 01:52 UTCGHSA enrichment
  19. 2026-08-09 13:47 UTCEPSS rescore
  20. 2026-08-09 13:06 UTCGHSA enrichment
  21. 2026-08-09 00:20 UTCEG score recompute
  22. 2026-08-09 00:20 UTCGHSA enrichment
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 11:33 UTCGHSA enrichment
  25. 2026-08-07 22:47 UTCEG score recompute
  26. 2026-08-07 22:47 UTCGHSA enrichment
  27. 2026-08-07 10:01 UTCGHSA enrichment
  28. 2026-08-06 21:15 UTCEG score recompute
  29. 2026-08-06 21:15 UTCGHSA enrichment
  30. 2026-08-06 13:47 UTCEPSS rescore
  31. 2026-08-06 08:29 UTCGHSA enrichment
  32. 2026-08-05 19:43 UTCEG score recompute
  33. 2026-08-05 19:43 UTCGHSA enrichment
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-05 06:57 UTCGHSA enrichment
  37. 2026-08-04 18:09 UTCEG score recompute
  38. 2026-08-04 18:09 UTCGHSA enrichment
  39. 2026-08-04 15:10 UTCEPSS rescore
  40. 2026-08-04 10:39 UTCEPSS rescore
  41. 2026-08-04 05:22 UTCGHSA enrichment
  42. 2026-08-03 16:36 UTCEG score recompute
  43. 2026-08-03 16:36 UTCGHSA enrichment
  44. 2026-08-03 15:28 UTCEG score recompute
  45. 2026-08-03 15:28 UTCGHSA enrichment
  46. 2026-08-03 11:28 UTCEG score recompute
  47. 2026-08-03 11:27 UTCGHSA enrichment
  48. 2026-08-03 02:17 UTCEG score recompute
  49. 2026-08-03 02:17 UTCGHSA enrichment
  50. 2026-08-02 13:30 UTCEG score recompute
  51. 2026-08-02 12:39 UTCEG score recompute
  52. 2026-08-02 12:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-68581?
CVE-2026-68581 is a high vulnerability published on August 2, 2026. Vikunja versions 0.22.0 through 2.3.0 fail to validate the principal type in API token management. Because user IDs and link-share IDs are independent numeric sequences and both resolve through a generic web.Auth.GetID() interface, a link-share JWT whose numeric ID equals a target user's ID is…
When was CVE-2026-68581 disclosed?
CVE-2026-68581 was first published in the National Vulnerability Database on August 2, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68581 actively exploited?
CVE-2026-68581 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 74.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68581?
CVE-2026-68581 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-68581?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68581, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-68581

Explore →

Is Your Infrastructure Affected by CVE-2026-68581?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs