Security readout for executives and security teams
Plain-English summary
Prompty’s TypeScript loader could run JavaScript hidden in a .prompty prompt file. If a vulnerable application loads an attacker-supplied prompt, that file can execute code in the loading process. The issue affects @prompty/core 2.0.0-alpha.1 through versions before 2.0.0-beta.3.
Executive priority
Treat as high priority where Prompty loads externally supplied or repository-sourced prompt files. The business risk is code execution inside AI application tooling, which can affect secrets, builds, or runtime systems depending on where prompts are loaded.
Technical view
The loader used gray-matter without disabling executable js and javascript frontmatter engines. A .prompty file using JavaScript frontmatter could trigger arbitrary JavaScript execution during prompt parsing. The CVE maps to CWE-94 and has CVSS 4.0 score 8.7.
Likely exposure
Exposure is likely limited to systems using Microsoft Prompty @prompty/core TypeScript loader versions >=2.0.0-alpha.1 and <2.0.0-beta.3, especially where .prompty files are imported from users, repositories, plugins, or automation pipelines.
Exploitation context
The provided sources do not show active exploitation, and KEV is false. Exploitation requires a vulnerable loader to process an attacker-controlled .prompty file. No exploit code or operational abuse details are included in the source bundle.
Researcher notes
Focus validation on the TypeScript loader path and gray-matter frontmatter behavior. The public bundle names the fixed commit and advisory, but does not provide evidence of exploitation or broader affected products beyond Microsoft Prompty @prompty/core.
Mitigation direction
- Upgrade @prompty/core to version 2.0.0-beta.3.
- Block untrusted .prompty files until vulnerable versions are removed.
- Review vendor advisory and commit for official remediation details.
- Restrict prompt sources to trusted repositories and approved release artifacts.
Validation and detection
- Inventory @prompty/core package versions across applications and pipelines.
- Identify code paths that load .prompty files with the TypeScript loader.
- Review whether .prompty files can come from users, CI, plugins, or external repositories.
- Confirm the fixed version is deployed in runtime and build environments.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-53597 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——GitHub_MVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/microsoft/prompty/security/advisories/GHSA-c4gh-rv8h-q9vwCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/microsoft/prompty/commit/c27402da2487075be577f06aa79df627fb9d6853CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.