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.
CVE-2026-54660
HIGHPre-NVD 7.47.4
EchelonGraph scoreLOW confidence
This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.4
- EG Score
- 7.4(low)
- EG Risk
- 38(Track)EG Risk 38/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity74% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 29, 2026
Last Modified
July 29, 2026
Advisory Details (4)
Auto-updated Jul 29, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available
v13.12.2
Patch available: acacode/swagger-typescript-api v13.12.2
https://github.com/acacode/swagger-typescript-api/releases/tag/v13.12.2github_commit Patch Available
commit 306d59acb8ff (acacode/swagger-typescript-api)
Patch available: acacode/swagger-typescript-api v13.12.2 (contains commit 306d59acb8ff)
https://github.com/acacode/swagger-typescript-api/commit/306d59acb8ffbb00f953f807b97234b21f51d9degithub_pr Patch Available
Security/fixing vulnerabilities
Patch available: acacode/swagger-typescript-api v13.12.2 (PR #1779 merged 2026-06-08)
https://github.com/acacode/swagger-typescript-api/pull/1779github Patch Available🟡 PoC Available
Authorization-token exfiltration via spec `$ref`; generator forwards `--authorizationToken` to cross-origin `$ref` URLs without same-origin check, allowing a malicious spec to steal the developer's bearer token · Advisory · acacode/swagger-typescript-api · GitHub
https://github.com/acacode/swagger-typescript-api/security/advisories/GHSA-h754-fxp7-88wxVendor Advisories for CVE-2026-54660(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(4)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-29 15:21 UTCEG score recompute
- 2026-07-29 14:48 UTCEG score recompute
- 2026-07-29 14:47 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-918 · CWE-522 · CWE-200
Frequently asked(4)
What is CVE-2026-54660?
CVE-2026-54660 is a high vulnerability published on July 29, 2026. 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…
When was CVE-2026-54660 disclosed?
CVE-2026-54660 was first published in the National Vulnerability Database on July 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-54660?
CVE-2026-54660 has a CVSS v3 base score of 7.4 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-54660?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54660, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-54660
Is Your Infrastructure Affected by CVE-2026-54660?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.