CVE-2026-54660

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. 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: epss, secondary
Elevated
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
49(Track)
EG Risk 49/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 computed
Severity74% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 29, 2026

Last Modified

July 30, 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.2
github_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/306d59acb8ffbb00f953f807b97234b21f51d9de
github_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/1779
github 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-88wx

Vendor 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.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
swagger-typescript-api—13.12.2—

Weakness Classification(4)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 49× 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.

  1. 2026-09-15 08:05 UTCEG score recompute
  2. 2026-09-15 03:11 UTCEPSS rescore
  3. 2026-09-14 04:26 UTCEG score recompute
  4. 2026-09-13 16:47 UTCEPSS rescore
  5. 2026-09-13 01:37 UTCEG score recompute
  6. 2026-09-11 22:07 UTCEG score recompute
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-10 19:51 UTCEG score recompute
  9. 2026-09-10 09:35 UTCEPSS rescore
  10. 2026-09-09 07:48 UTCEG score recompute
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-07 20:50 UTCEG score recompute
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 22:41 UTCEG score recompute
  15. 2026-09-06 13:47 UTCEPSS rescore
  16. 2026-09-05 19:06 UTCEG score recompute
  17. 2026-09-05 05:13 UTCEG score recompute
  18. 2026-09-04 11:55 UTCEG score recompute
  19. 2026-09-04 05:06 UTCEPSS rescore
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 22:47 UTCEG score recompute
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-31 01:35 UTCEG score recompute
  25. 2026-08-30 19:17 UTCEPSS rescore
Show 62 more
  1. 2026-08-30 12:27 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-29 23:19 UTCEG score recompute
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-27 22:34 UTCEG score recompute
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 19:39 UTCEG score recompute
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-26 02:29 UTCEG score recompute
  10. 2026-08-25 13:49 UTCEPSS rescore
  11. 2026-08-25 00:13 UTCEG score recompute
  12. 2026-08-24 11:05 UTCEG score recompute
  13. 2026-08-23 08:49 UTCEG score recompute
  14. 2026-08-23 00:19 UTCEPSS rescore
  15. 2026-08-22 06:33 UTCEG score recompute
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 04:17 UTCEG score recompute
  18. 2026-08-20 22:55 UTCEPSS rescore
  19. 2026-08-20 01:58 UTCEG score recompute
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 23:40 UTCEG score recompute
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-17 21:23 UTCEG score recompute
  24. 2026-08-17 13:47 UTCEPSS rescore
  25. 2026-08-16 19:08 UTCEG score recompute
  26. 2026-08-16 14:56 UTCEPSS rescore
  27. 2026-08-16 06:00 UTCEG score recompute
  28. 2026-08-16 02:14 UTCEPSS rescore
  29. 2026-08-15 03:45 UTCEG score recompute
  30. 2026-08-15 01:30 UTCEPSS rescore
  31. 2026-08-14 01:29 UTCEG score recompute
  32. 2026-08-13 22:00 UTCEPSS rescore
  33. 2026-08-12 23:14 UTCEG score recompute
  34. 2026-08-12 13:51 UTCEPSS rescore
  35. 2026-08-11 20:58 UTCEG score recompute
  36. 2026-08-11 07:50 UTCEG score recompute
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-09 16:28 UTCEG score recompute
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-09 03:20 UTCEG score recompute
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-08 01:05 UTCEG score recompute
  43. 2026-08-06 22:49 UTCEG score recompute
  44. 2026-08-06 13:47 UTCEPSS rescore
  45. 2026-08-05 20:22 UTCEG score recompute
  46. 2026-08-05 19:17 UTCEPSS rescore
  47. 2026-08-04 18:05 UTCEG score recompute
  48. 2026-08-04 15:10 UTCEPSS rescore
  49. 2026-08-04 10:39 UTCEPSS rescore
  50. 2026-08-03 15:43 UTCEG score recompute
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-02 13:28 UTCEG score recompute
  53. 2026-08-02 02:27 UTCEPSS rescore
  54. 2026-08-01 11:12 UTCEG score recompute
  55. 2026-08-01 04:16 UTCEPSS rescore
  56. 2026-07-30 19:43 UTCEG score recompute
  57. 2026-07-30 16:28 UTCEPSS rescore
  58. 2026-07-30 14:38 UTCEG score recompute
  59. 2026-07-30 14:08 UTCEG score recompute
  60. 2026-07-29 15:21 UTCEG score recompute
  61. 2026-07-29 14:48 UTCEG score recompute
  62. 2026-07-29 14:47 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

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, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54660 actively exploited?
CVE-2026-54660 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.4% of all scored CVEs.
What is the CVSS score of CVE-2026-54660?
CVE-2026-54660 has a CVSS v3 base score of 7.4 (NVD).
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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54660

Explore →

Is Your Infrastructure Affected by CVE-2026-54660?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs