CVE-2026-54766

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

Vikunja is an open-source self-hosted task management platform. From 0.21.0 until 2.4.0, the project duplication operation in pkg/models/project_duplicate.go allows an authenticated user who can read a source project to place its duplicate beneath an arbitrary target parent project. ProjectDuplicate.CanCreate calls parent.CanCreate on an unhydrated Project containing only the body supplied parent_project_id instead of calling parent.CanWrite, so the target parent write-permission check is skipped. The ordinary project creation path enforces that permission, but PUT /api/v1/projects/{project}/duplicate does not, allowing attacker-owned content to be injected into another user or team project hierarchy. This issue is fixed in version 2.4.0.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
28(Track)
EG Risk 28/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
Severity53% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
24%
KEV
Not listed

Published

August 28, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Aug 28, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

Project duplication bypasses write-permission check on the target parent project · Advisory · go-vikunja/vikunja · GitHub

https://github.com/go-vikunja/vikunja/security/advisories/GHSA-f27p-pw2p-9pr4
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_pr

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 d911caaa11c7 (go-vikunja/vikunja)

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

https://github.com/go-vikunja/vikunja/commit/d911caaa11c748c3abc6b98b3189afea2677bcb0

Vendor Advisories for CVE-2026-54766(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
code.vikunja.io/api—2.4.0—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 38× 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-09-20 01:47 UTCEG score recompute
  2. 2026-09-19 03:39 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 05:31 UTCEG score recompute
  5. 2026-09-17 19:31 UTCEPSS rescore
  6. 2026-09-17 07:22 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 09:11 UTCEG score recompute
  9. 2026-09-16 05:15 UTCEPSS rescore
  10. 2026-09-15 10:07 UTCEG score recompute
  11. 2026-09-15 03:11 UTCEPSS rescore
  12. 2026-09-14 11:57 UTCEG score recompute
  13. 2026-09-13 16:47 UTCEPSS rescore
  14. 2026-09-12 15:40 UTCEG score recompute
  15. 2026-09-11 17:32 UTCEG score recompute
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-10 19:23 UTCEG score recompute
  18. 2026-09-10 09:35 UTCEPSS rescore
  19. 2026-09-09 00:53 UTCEG score recompute
  20. 2026-09-08 22:01 UTCEPSS rescore
  21. 2026-09-07 04:37 UTCEG score recompute
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-06 06:28 UTCEG score recompute
  24. 2026-09-05 08:20 UTCEG score recompute
  25. 2026-09-04 10:11 UTCEG score recompute
Show 13 more
  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-03 12:01 UTCEG score recompute
  3. 2026-09-02 14:12 UTCEPSS rescore
  4. 2026-09-01 15:24 UTCEG score recompute
  5. 2026-09-01 13:54 UTCEPSS rescore
  6. 2026-09-01 04:40 UTCEPSS rescore
  7. 2026-08-31 17:14 UTCEG score recompute
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 19:05 UTCEG score recompute
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-28 20:24 UTCEG score recompute▲ 5.30
  12. 2026-08-28 20:24 UTCNVD updateCVSS v3 → 5.3 · CVSS v4 → 5.3
  13. 2026-08-28 17:12 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54766?
CVE-2026-54766 is a medium vulnerability published on August 28, 2026. Vikunja is an open-source self-hosted task management platform. From 0.21.0 until 2.4.0, the project duplication operation in pkg/models/projectduplicate.go allows an authenticated user who can read a source project to place its duplicate beneath an arbitrary target parent project.…
When was CVE-2026-54766 disclosed?
CVE-2026-54766 was first published in the National Vulnerability Database on August 28, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54766 actively exploited?
CVE-2026-54766 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 75.5% of all scored CVEs.
What is the CVSS score of CVE-2026-54766?
CVE-2026-54766 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-54766?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54766, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54766

Explore →

Is Your Infrastructure Affected by CVE-2026-54766?

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

Start Free Scan →Browse All CVEs