CVE-2026-19370

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory (severity: LOW) published 2026-08-10. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
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.

A vulnerability was determined in bartekke8it56w2 new-mcp 0.1.0. This impacts the function fs.writeFileSync/fs.existsSync/fs.readFileSync of the file index.ts of the component geminithinking. This manipulation of the argument sessionCommand/sessionPath causes path traversal. The attack requires local access. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
24(Track)
EG Risk 24/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

August 9, 2026

Last Modified

August 12, 2026

Advisory Details (2)

Auto-updated Aug 9, 2026
No patch confirmed yet.
generic

Arbitrary Session File Read/Write via sessionPath in bartekke8it56w2/new-mcp · Issue #10 · bartekke8it56w2/new-mcp · GitHub

https://github.com/bartekke8it56w2/new-mcp/issues/10
generic

GitHub - bartekke8it56w2/new-mcp · GitHub

https://github.com/bartekke8it56w2/new-mcp/

Vendor Advisories for CVE-2026-19370(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 20× in last 7d / 39× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 14:17 UTCEG score recompute
  3. 2026-08-20 14:17 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 14:37 UTCGHSA enrichment
  6. 2026-08-18 15:38 UTCEG score recompute
  7. 2026-08-18 15:38 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-17 15:37 UTCEG score recompute
  10. 2026-08-17 15:37 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-16 16:42 UTCEG score recompute
  13. 2026-08-16 16:42 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 17:48 UTCEG score recompute
  17. 2026-08-15 17:48 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 18:53 UTCEG score recompute
  20. 2026-08-14 18:53 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 19:58 UTCGHSA enrichment
  23. 2026-08-12 21:03 UTCGHSA enrichment
  24. 2026-08-12 16:17 UTCEG score recompute
  25. 2026-08-12 16:17 UTCGHSA enrichment
Show 14 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-11 17:22 UTCEG score recompute
  3. 2026-08-11 17:22 UTCGHSA enrichment
  4. 2026-08-11 13:42 UTCEPSS rescore
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-10 18:26 UTCEG score recompute
  7. 2026-08-10 18:26 UTCGHSA enrichment
  8. 2026-08-10 18:24 UTCNVD updateCVSS v4 → 1.9
  9. 2026-08-10 17:35 UTCEG score recompute
  10. 2026-08-10 17:35 UTCGHSA enrichment
  11. 2026-08-10 17:35 UTCMITRE cvelistV5CVSS v4 → 4.8
  12. 2026-08-09 22:17 UTCNVD updateCVSS v4 → 1.9
  13. 2026-08-09 22:16 UTCEG score recompute
  14. 2026-08-09 22:16 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19370?
CVE-2026-19370 is a medium vulnerability published on August 9, 2026. A vulnerability was determined in bartekke8it56w2 new-mcp 0.1.0. This impacts the function fs.writeFileSync/fs.existsSync/fs.readFileSync of the file index.ts of the component geminithinking. This manipulation of the argument sessionCommand/sessionPath causes path traversal. The attack requires…
When was CVE-2026-19370 disclosed?
CVE-2026-19370 was first published in the National Vulnerability Database on August 9, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19370 actively exploited?
CVE-2026-19370 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 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-19370?
CVE-2026-19370 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-19370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19370, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-19370?

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

Start Free Scan →Browse All CVEs