Code Injection in @prompty/core (CVE-2026-53597)
Summary
Code injection in @prompty/core (CVE-2026-53597). Risk of unauthorized operations or information disclosure. Exploitable via javascript. Mitigation: upgrade to 2.0.0-beta.3 or later.
Original description
The description as published by the source.
Prompty is a markdown file format (.prompty) for LLM prompts. From 2.0.0-alpha.1 until 2.0.0-beta.3, the @prompty/core TypeScript loader in runtime/typescript/packages/core/src/core/loader.ts used gray-matter without overriding executable js and javascript frontmatter engines, allowing an attacker-controlled .prompty file with ---js frontmatter to execute arbitrary JavaScript during prompt loading. This issue is fixed in version 2.0.0-beta.3.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53597 has been found in @prompty/core.
Attackers can target a specific entry point like javascript over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @prompty/core to 2.0.0-beta.3 or later.
If unsure, ask your IT team or search "@prompty/core CVE-2026-53597" on the vendor's site.
CVE-2026-53597 (@prompty/core) — CWE-94
Attack surface: javascript / c27402da2487075be577f06aa79df627fb9d6853
Patched: 2.0.0-beta.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in @prompty/core. Attackers reach the vulnerable code path via javascript.
Check the vendor advisory for the affected versions of @prompty/core. Attack surface: javascript / c27402da2487075be577f06aa79df627fb9d6853.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.0.0-beta.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@prompty/core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@prompty/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@prompty/coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @prompty/core to 2.0.0-beta.3ステージング環境で 2.0.0-beta.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com