CVE-2026-53598 microsoft CVE debrief

Who should care

Users of Prompty markdown file format (.prompty) for LLM prompts, especially those using versions prior to 2.0.0-beta.2, should be aware of this vulnerability. Affected operators, platforms, vulnerability-management teams, and security teams should review official advisories and plan vendor-supported updates or mitigations. They should also monitor for suspicious activity and review compensating controls for exposed systems.

Technical summary

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. This allowed an attacker-controlled prompt file to read local files through absolute paths, .. traversal, or symlink escapes. Users of Prompty should update to version 2.0.0-beta.2 or later to mitigate this vulnerability. The technical summary provides affected product context, defensive impact, and source-grounded technical framing.

Defensive priority

High priority due to CVSS score of 7.5 and potential for local file reads.

Recommended defensive actions

• Update Prompty to version 2.0.0-beta.2 or later
• Restrict access to .prompty files
• Monitor for suspicious activity
• Review compensating controls for exposed systems
• Check relevant monitoring, detection, and logs for exposed assets
• Track exceptions and retest remediated assets
• Confirm whether affected product deployments exist in managed environments

Evidence notes

Evidence is based on official CVE and NVD records, as well as source references from GitHub. The vulnerability allows an attacker-controlled prompt file to read local files through absolute paths, .. traversal, or symlink escapes. Users should verify affected deployments and review official advisories for scope and guidance. Defenders should focus on updating Prompty to version 2.0.0-beta.2 or later and restricting access to .prompty files.

Official resources