CVE-2026-68581

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-51991 (ENISA EUVD) · GHSA-9jrx-vmh8-c6xw (GitHub Security Advisories) · GHSA-vvcv-vpph-h844 (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 8.1Exploit: No code on recordExposed 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.1HIGHhigh confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
40th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 2, 2026

Last Modified

October 23, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit, github.
Web pageMentions a patch (unverified)

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 advisoryMentions a patch (unverified)

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gocode.vikunja.io/api @ 2.4.0 (fixes >= 0.22.0, <= 2.3.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
code.vikunja.io/api—
  • 0.22.0 up to 2.4.0: fixed in 2.4.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 50× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 253 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 153 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-68581?
CVE-2026-68581 is a high-severity vulnerability; its CVE record was 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 made public?
CVE-2026-68581 was made public on July 19, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 2, 2026. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
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 (40th 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

See which npm, PyPI, Go, and Maven packages are affected by 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