Skip to content
Applications

CVE-2026-54666

8.3
High
EPSS 0.29%Patch availableJul 30, 2026

Template-literal injection in swagger-typescript-api allows execution in generated API clients.

common questions

Is CVE-2026-54666 being exploited?

Not confirmed. CVE-2026-54666 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.29% probability of exploitation in the next 30 days.

How severe is CVE-2026-54666?

CVE-2026-54666 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-54666?

Yes. A fix has been recorded for CVE-2026-54666. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-54666 affect?

CVE-2026-54666 affects swagger-typescript-api < 13.12.2, Generated Fetch/Axios API clients from affected versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-54666?

Upgrade to swagger-typescript-api v13.12.2; sanitize OpenAPI paths if delay unavoidable.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
swagger-typescript-api < 13.12.2Generated Fetch/Axios API clients from affected versions
impact

Attacker-controlled OpenAPI path with ${...} can execute arbitrary JavaScript when generated client methods run, enabling code execution or data exfiltration.

action required

Immediate action required

affected versions
acacode swagger-typescript-api
  • affected< 13.12.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free