CVE-2026-55065

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. 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-67832 (ENISA EUVD) · GHSA-gg93-x632-9ccv (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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 is an open-source self-hosted task management platform. From 0.24.6 until 2.4.0, DELETE /api/v1/projects/:project/views/:view permits an authenticated user to supply a view identifier from another project while authorizing only against an attacker-controlled project identifier. ProjectView.CanDelete in pkg/models/project_view_permissions.go does not establish that the view belongs to the path project, and ProjectView.Delete in pkg/models/project_view.go continues after the scoped project_views delete affects no rows. Its subsequent deletes select task_buckets and task_positions only by project_view_id, allowing cross-tenant destruction of Kanban assignments and ordering while leaving the victim view and tasks intact. This issue is fixed in version 2.4.0.

CVSS v3
8.1
EG Score
8.1HIGHmedium 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.5%
EPSS %ILE
43rd
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 or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 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 or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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 28, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 28, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Improper Authorization and Authorization Bypass Through User-Controlled Key in code.vikunja.io/api · Advisory · go-vikunja/vikunja · GitHub

https://github.com/go-vikunja/vikunja/security/advisories/GHSA-gg93-x632-9ccv
GitHub release Patch Available

v2.4.0

Patch available: go-vikunja/vikunja v2.4.0

https://github.com/go-vikunja/vikunja/releases/tag/v2.4.0
GitHub pull request

Fix security vulnerabilities

Fix merged in go-vikunja/vikunja PR #3239 on 2026-07-19 — awaiting tagged release

https://github.com/go-vikunja/vikunja/pull/3239
GitHub commit

commit 6895a7765ef1 (go-vikunja/vikunja)

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

https://github.com/go-vikunja/vikunja/commit/6895a7765ef1667be4b79df29549d33b9e1ca9ca

Vendor Advisories for CVE-2026-55065(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.24.6, < 2.4.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.24.6 up to 2.4.0: fixed in 2.4.0
  • 0.24.6 on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 48× 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 112 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 12 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55065?
CVE-2026-55065 is a high-severity vulnerability; its CVE record was published on August 28, 2026. Vikunja is an open-source self-hosted task management platform. From 0.24.6 until 2.4.0, DELETE /api/v1/projects/:project/views/:view permits an authenticated user to supply a view identifier from another project while authorizing only against an attacker-controlled project identifier.…
When was the CVE record for CVE-2026-55065 published?
The CVE record for CVE-2026-55065 was published on August 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55065 actively exploited?
CVE-2026-55065 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55065?
CVE-2026-55065 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-55065?
A fix for CVE-2026-55065 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55065 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-55065

Explore →

Is Your Infrastructure Affected by CVE-2026-55065?

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

Book a Demo →Browse All CVEs