Vulnerability in swagger-typescript-api (CVE-2026-54661)
Summary
Vulnerability in swagger-typescript-api (CVE-2026-54661). Successful exploitation can lead to full system takeover. Exploitable via HttpClient. Mitigation: upgrade to 13.12.2 or later.
Original description
The description as published by the source.
swagger-typescript-api generates API clients for Fetch or Axios from an OpenAPI Specification. Prior to 13.12.2, templates/base/http-clients/axios-http-client.ejs interpolates servers[0].url from src/code-gen-process.ts into the HttpClient constructor without escaping, allowing an attacker-controlled OpenAPI spec to inject code that executes when new HttpClient() or new Api() is constructed. This issue is fixed in version 13.12.2.
Source: GitHub Security Advisories (Global) 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-54661 has been found in swagger-typescript-api.
Attackers can target a specific entry point like HttpClient 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-54661" on the vendor's site.
CVE-2026-54661 (swagger-typescript-api) — CWE-1336 / CVSS v3 8.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: HttpClient / apiConfig.baseUrl / createApiConfig / baseUrl
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.
A vulnerability (CWE-1336) exists in swagger-typescript-api. Attackers reach the vulnerable code path via HttpClient without authentication.
Check the vendor advisory for the affected versions of swagger-typescript-api. Attack surface: HttpClient / apiConfig.baseUrl / createApiConfig / baseUrl.
Severity: High (CVSS 8.3/10). Successful exploitation can lead to full system takeover.
Update to 13.12.2.
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 'swagger-typescript-api' . 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 'swagger-typescript-api' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
swagger-typescript-apiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade swagger-typescript-api to 13.12.2ステージング環境で 13.12.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com