CVE-2026-51873

UNRATEDCVSS · not yet scoredTrending — 5 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS v2: —Exploit: None knownExposed services: Not assessed

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

Devika v1.0 is vulnerable to Directory Traversal in the Coder.save_code_to_project function, which allows attackers to write files outside the intended project workspace.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.3%
EPSS %ILE
16th
KEV
Not listed

Published

October 1, 2026

Last Modified

October 2, 2026

References (2)

Vendor Advisories for CVE-2026-51873(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 9× 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-10-04 23:22 UTCEPSS rescore
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-02 18:16 UTCGHSA enrichment
  4. 2026-10-02 18:16 UTCEG score recompute
  5. 2026-10-02 18:16 UTCGHSA enrichment
  6. 2026-10-02 17:56 UTCEPSS rescore
  7. 2026-10-01 22:17 UTCNVD update
  8. 2026-10-01 21:37 UTCEG score recompute
  9. 2026-10-01 21:35 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-51873?
CVE-2026-51873 is a publicly disclosed vulnerability published on October 1, 2026. Devika v1.0 is vulnerable to Directory Traversal in the Coder.savecodeto_project function, which allows attackers to write files outside the intended project workspace.
When was CVE-2026-51873 disclosed?
CVE-2026-51873 was first published on October 1, 2026, with the most recent update on October 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-51873 actively exploited?
CVE-2026-51873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-51873?
No fix for CVE-2026-51873 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-51873 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-51873?

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

Book a Demo →Browse All CVEs