Information Disclosure in swagger-typescript-api (CVE-2026-54660)
Summary
Vulnerability in swagger-typescript-api (CVE-2026-54660). Confidential information can be exposed externally. Exploitable via GET /exfil-endpoint/data.json. 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 OpenAPI specifications. Prior to 13.12.2, src/resolved-swagger-schema.ts getRemoteRequestHeaders forwards --authorizationToken to every URL fetched by fetchRemoteSchemaDocument while warmUpRemoteSchemasCache resolves external $ref URLs, allowing an attacker-controlled OpenAPI spec to exfiltrate the developer or CI bearer token to a cross-origin endpoint. 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-54660 has been found in swagger-typescript-api.
Attackers can target a specific entry point like GET /exfil-endpoint/data.json over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.4/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-54660" on the vendor's site.
CVE-2026-54660 (swagger-typescript-api) — CWE-200 / CVSS v3 7.4
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: GET /exfil-endpoint/data.json / Authorization header / Authorization / this.config.url
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.
Information disclosure (CWE-200) exists in swagger-typescript-api. Attackers reach the vulnerable code path via GET /exfil-endpoint/data.json without authentication.
Check the vendor advisory for the affected versions of swagger-typescript-api. Attack surface: GET /exfil-endpoint/data.json / Authorization header / Authorization / this.config.url.
Severity: High (CVSS 7.4/10). Confidential information can be exposed externally.
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 GET /exfil-endpoint/data.json requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /exfil-endpoint/data.json' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /exfil-endpoint/data.jsonへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade swagger-typescript-api to 13.12.2ステージング環境で 13.12.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /exfil-endpoint/data.json on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
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