← Back
CVE-2026-54664
high
CVSS 8.3
Vulnerability in swagger-typescript-api (CVE-2026-54664)
Summary
vulnerability in swagger-typescript-api (CVE-2026-54664). Successful exploitation can lead to full system takeover. Exploitable via ``enum``. Mitigation: upgrade to `13.12.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54664** has been found in swagger-typescript-api.
Attackers can target a specific entry point like ``enum`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.3/10.
What to do: upgrade swagger-typescript-api to **13.12.2** or later.
If unsure, ask your IT team or search "swagger-typescript-api CVE-2026-54664" on the vendor's site.
CVE-2026-54664 (swagger-typescript-api) — CWE-74 / CVSS v3 8.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `enum` / `import` / `Ts.StringValue` / `escapeJSDocContent`
Patched: `13.12.2` — 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.
❓ What is the problem
**A vulnerability** (CWE-74) exists in swagger-typescript-api. Attackers reach the vulnerable code path via ``enum`` without authentication.
📍 Affected scope
swagger-typescript-api — . Attack surface: `enum` / `import` / `Ts.StringValue` / `escapeJSDocContent`.
🔥 Severity
Severity: High (CVSS 8.3/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **13.12.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'swagger-typescript-api' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'swagger-typescript-api' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `swagger-typescript-api` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade swagger-typescript-api to 13.12.2ステージング環境で 13.12.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
swagger-typescript-api
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"13.12.2"}]}]