CVE-2026-68581

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM 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.5%CVSS: 8.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100CISA SSVC

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%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 2, 2026

Last Modified

September 8, 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 18× in last 7d / 85× 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.

Showing the most recent 100 of 209 total refreshes for this CVE.

  1. 2026-10-04 23:47 UTCEG score recompute
  2. 2026-10-04 23:47 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 06:23 UTCEG score recompute
  5. 2026-10-04 06:23 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-03 02:42 UTCEG score recompute
  8. 2026-10-03 02:42 UTCGHSA enrichment
  9. 2026-10-02 17:56 UTCEPSS rescore
  10. 2026-10-02 10:26 UTCEG score recompute
  11. 2026-10-02 10:26 UTCGHSA enrichment
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-10-01 15:41 UTCGHSA enrichment
  14. 2026-10-01 02:40 UTCEG score recompute
  15. 2026-10-01 02:40 UTCGHSA enrichment
  16. 2026-09-30 15:03 UTCEPSS rescore
  17. 2026-09-29 06:45 UTCEG score recompute
  18. 2026-09-29 06:45 UTCGHSA enrichment
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 07:08 UTCGHSA enrichment
  21. 2026-09-27 18:20 UTCEG score recompute
  22. 2026-09-27 18:20 UTCGHSA enrichment
  23. 2026-09-27 13:48 UTCEPSS rescore
  24. 2026-09-26 15:59 UTCEPSS rescore
  25. 2026-09-25 04:49 UTCEG score recompute
Show 75 more
  1. 2026-09-25 04:49 UTCGHSA enrichment
  2. 2026-09-24 12:52 UTCGHSA enrichment
  3. 2026-09-23 23:49 UTCEG score recompute
  4. 2026-09-23 23:49 UTCGHSA enrichment
  5. 2026-09-23 17:54 UTCEPSS rescore
  6. 2026-09-23 10:17 UTCGHSA enrichment
  7. 2026-09-22 21:31 UTCEG score recompute
  8. 2026-09-22 21:31 UTCGHSA enrichment
  9. 2026-09-22 06:50 UTCEG score recompute
  10. 2026-09-22 06:50 UTCGHSA enrichment
  11. 2026-09-21 21:09 UTCEPSS rescore
  12. 2026-09-20 20:58 UTCEG score recompute
  13. 2026-09-20 20:58 UTCGHSA enrichment
  14. 2026-09-20 20:16 UTCEPSS rescore
  15. 2026-09-19 23:30 UTCEG score recompute
  16. 2026-09-19 23:30 UTCGHSA enrichment
  17. 2026-09-19 03:55 UTCEG score recompute
  18. 2026-09-19 03:55 UTCGHSA enrichment
  19. 2026-09-18 19:28 UTCEPSS rescore
  20. 2026-09-18 14:51 UTCGHSA enrichment
  21. 2026-09-18 01:13 UTCEG score recompute
  22. 2026-09-18 01:13 UTCGHSA enrichment
  23. 2026-09-17 01:19 UTCEG score recompute
  24. 2026-09-17 01:19 UTCGHSA enrichment
  25. 2026-09-16 14:08 UTCEPSS rescore
  26. 2026-09-16 05:57 UTCEG score recompute
  27. 2026-09-16 05:57 UTCGHSA enrichment
  28. 2026-09-16 05:15 UTCEPSS rescore
  29. 2026-09-15 17:11 UTCEG score recompute
  30. 2026-09-15 17:11 UTCGHSA enrichment
  31. 2026-09-15 02:48 UTCGHSA enrichment
  32. 2026-09-14 13:19 UTCGHSA enrichment
  33. 2026-09-13 23:41 UTCEG score recompute
  34. 2026-09-13 23:41 UTCGHSA enrichment
  35. 2026-09-13 10:55 UTCGHSA enrichment
  36. 2026-09-12 21:59 UTCEG score recompute
  37. 2026-09-12 21:59 UTCGHSA enrichment
  38. 2026-09-12 09:11 UTCGHSA enrichment
  39. 2026-09-11 20:24 UTCEG score recompute
  40. 2026-09-11 20:24 UTCGHSA enrichment
  41. 2026-09-11 14:53 UTCEPSS rescore
  42. 2026-09-11 09:37 UTCEPSS rescore
  43. 2026-09-11 07:32 UTCGHSA enrichment
  44. 2026-09-10 18:46 UTCEG score recompute
  45. 2026-09-10 18:46 UTCGHSA enrichment
  46. 2026-09-10 03:16 UTCGHSA enrichment
  47. 2026-09-09 09:50 UTCEG score recompute
  48. 2026-09-09 09:50 UTCGHSA enrichment
  49. 2026-09-08 22:01 UTCEPSS rescore
  50. 2026-09-08 21:03 UTCGHSA enrichment
  51. 2026-09-07 19:08 UTCEG score recompute
  52. 2026-09-07 19:08 UTCGHSA enrichment
  53. 2026-09-07 16:01 UTCEPSS rescore
  54. 2026-09-06 20:44 UTCEG score recompute
  55. 2026-09-06 20:44 UTCGHSA enrichment
  56. 2026-09-06 13:47 UTCEPSS rescore
  57. 2026-09-06 07:29 UTCGHSA enrichment
  58. 2026-09-05 18:42 UTCEG score recompute
  59. 2026-09-05 18:42 UTCGHSA enrichment
  60. 2026-09-05 15:31 UTCEPSS rescore
  61. 2026-09-05 05:37 UTCGHSA enrichment
  62. 2026-09-04 16:50 UTCEG score recompute
  63. 2026-09-04 16:50 UTCGHSA enrichment
  64. 2026-09-04 05:07 UTCEPSS rescore
  65. 2026-09-04 03:39 UTCGHSA enrichment
  66. 2026-09-03 09:00 UTCEG score recompute
  67. 2026-09-03 09:00 UTCGHSA enrichment
  68. 2026-09-02 14:12 UTCEPSS rescore
  69. 2026-09-01 22:22 UTCEG score recompute
  70. 2026-09-01 22:22 UTCGHSA enrichment
  71. 2026-09-01 13:54 UTCEPSS rescore
  72. 2026-09-01 04:40 UTCEPSS rescore
  73. 2026-08-31 23:17 UTCGHSA enrichment
  74. 2026-08-30 23:43 UTCEG score recompute
  75. 2026-08-30 23:43 UTCGHSA enrichment

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 on August 2, 2026, with the most recent update on September 8, 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.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68581?
CVE-2026-68581 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68581?
A fix for CVE-2026-68581 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68581 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs