CVE-2026-54660

Received Received - Intake

Remote Code Execution in swagger-typescript-api

Publication date: 2026-07-29

Last updated on: 2026-07-29

Assigner: GitHub, Inc.

Description

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-29

Last Modified

2026-07-29

Generated

2026-07-30

AI Q&A

2026-07-30

EPSS Evaluated

N/A

NVD

CVE-2026-54660

Affected Vendors & Products

Vendor	Product	Version / Range
swagger_typescript_api	swagger_typescript_api	13.12.2

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
CWE-522	The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
CWE-200	The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-201	The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

Attack-Flow Graph

Executive Summary

swagger-typescript-api before 13.12.2 has a vulnerability where the getRemoteRequestHeaders function forwards an authorization token to all URLs fetched during schema resolution. This allows an attacker who controls an OpenAPI spec to exfiltrate the bearer token to a cross-origin endpoint.

Impact Analysis

If you use a vulnerable version of swagger-typescript-api, an attacker could steal your authentication token by tricking you into processing a malicious OpenAPI specification. This could lead to unauthorized access to your accounts or data.

Compliance Impact

This vulnerability could lead to unauthorized data access, potentially violating GDPR's data protection requirements or HIPAA's safeguards for protected health information. Token theft may result in compliance breaches depending on the data exposed.

Mitigation Strategies

Update swagger-typescript-api to version 13.12.2 or later to address the vulnerability. Review any OpenAPI specifications processed by the tool to ensure no malicious $ref URLs are present that could exfiltrate bearer tokens.

Hi! I’m here to help you understand CVE-2026-54660. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70