CVE-2026-54663 swagger-typescript-api vulnerable to Server-Side Request Forgery via spec `$ref`
An attacker can craft a malicious OpenAPI spec to force the generator to make requests to internal services, potentially exposing sensitive data.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-54663?
CVE-2026-54663 is a medium-severity server-side request forgery vulnerability in acacode swagger-typescript-api, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
swagger-typescript-api generates API clients for Fetch or Axios from OpenAPI specifications. Prior to 13.12.2, src/resolved-swagger-schema.ts warmUpRemoteSchemasCache resolves external $ref URLs and fetchRemoteSchemaDocument uses isHttpUrl to fetch any http or https target without private IP, redirect, DNS rebinding, or same-origin validation, allowing an attacker-controlled OpenAPI spec to make the generator issue requests to internal or link-local services. This issue is fixed in version 13.12.2.
Which versions are affected by CVE-2026-54663?
2 open source packages ship an affected version, including swagger-typescript-api.
| Package | Affected | Fixed in |
|---|---|---|
swagger-typescript-api npm | All versions | 13.12.2 |
swagger-typescript-api npm | All versions | 13.12.2 |
How do I fix CVE-2026-54663?
Upgrade swagger-typescript-api to 13.12.2 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-54663 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54663 exists.
Sources
Also known as GHSA-x36r-4347-pm5x.