CVE-2026-53598

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 1.1%, top 39% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

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

Prompty is a markdown file format (.prompty) for LLM prompts. Prior to 2.0.0-beta.2, Prompty loaders expanded ${file:...} references in .prompty frontmatter without enforcing that resolved paths stayed within the prompt directory or allowed roots, allowing an attacker-controlled prompt file to read local files through absolute paths, .. traversal, or symlink escapes. This issue is fixed in versions 2.0.0-beta.2.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
60.9%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 17, 2026

Advisory Details (1)

Auto-updated Jul 16, 2026
Patch available. Sources: github.
github Patch Available

Arbitrary file read via file reference expansion · Advisory · microsoft/prompty · GitHub

https://github.com/microsoft/prompty/security/advisories/GHSA-wxhm-2mq7-7697

Vendor Advisories for CVE-2026-53598(1)

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

Affected Packages

(4 across 4 ecosystems)
crates.io(1)
PackageVulnerable rangeFixed inDependents
prompty—2.0.0-beta.2—
npm(1)
PackageVulnerable rangeFixed inDependents
@prompty/core—2.0.0-beta.2—
NuGet(1)
PackageVulnerable rangeFixed inDependents
Prompty.Core0.2.3-beta2.0.0-beta.2—
PyPI(1)
PackageVulnerable rangeFixed inDependents
prompty0.1.1 ... 2.0.0b1 (47 versions)2.0.0b2—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 13× 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-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:19 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:35 UTCEG score recompute
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-17 14:15 UTCEG score recompute
  12. 2026-07-16 15:24 UTCEG score recompute
  13. 2026-07-16 15:23 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53598?
CVE-2026-53598 is a high vulnerability published on July 16, 2026. Prompty is a markdown file format (.prompty) for LLM prompts. Prior to 2.0.0-beta.2, Prompty loaders expanded ${file:...} references in .prompty frontmatter without enforcing that resolved paths stayed within the prompt directory or allowed roots, allowing an attacker-controlled prompt file to read…
When was CVE-2026-53598 disclosed?
CVE-2026-53598 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53598 actively exploited?
CVE-2026-53598 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53598?
CVE-2026-53598 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-53598?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53598, 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-53598

Explore →

Is Your Infrastructure Affected by CVE-2026-53598?

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

Start Free Scan →Browse All CVEs