CVE-2026-54660: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in acacode swagger-typescript-api
A vulnerability in swagger-typescript-api prior to version 13.12.2 allows exposure of sensitive bearer tokens. The issue occurs because the authorization token is forwarded to every URL fetched during schema resolution, enabling an attacker-controlled OpenAPI specification to exfiltrate the token to a cross-origin endpoint. This vulnerability has a high severity with a CVSS score of 7.4 and is fixed in version 13.12.2.
AI Analysis
Technical Summary
The swagger-typescript-api tool, used to generate API clients from OpenAPI specifications, had a vulnerability in versions before 13.12.2. Specifically, the src/resolved-swagger-schema.ts file's getRemoteRequestHeaders function forwarded the --authorizationToken to every URL fetched by fetchRemoteSchemaDocument during the warmUpRemoteSchemasCache process. This behavior allowed an attacker who could supply a malicious OpenAPI spec to cause the developer's or CI's bearer token to be sent to an external, cross-origin endpoint, resulting in exposure of sensitive information. The vulnerability is addressed by updating to version 13.12.2 where this token forwarding behavior is corrected.
Potential Impact
An attacker able to supply a malicious OpenAPI specification can cause the bearer token used for authorization to be leaked to an external endpoint. This exposure compromises confidentiality of sensitive tokens, potentially allowing unauthorized access to protected resources. The vulnerability does not impact integrity or availability directly but poses a significant risk due to token theft.
Mitigation Recommendations
Upgrade swagger-typescript-api to version 13.12.2 or later, where this vulnerability is fixed. There is no indication of alternative mitigations or temporary workarounds. Patch status is not explicitly stated in the vendor advisory, but the description confirms the fix is included in version 13.12.2.
CVE-2026-54660: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in acacode swagger-typescript-api
Description
A vulnerability in swagger-typescript-api prior to version 13.12.2 allows exposure of sensitive bearer tokens. The issue occurs because the authorization token is forwarded to every URL fetched during schema resolution, enabling an attacker-controlled OpenAPI specification to exfiltrate the token to a cross-origin endpoint. This vulnerability has a high severity with a CVSS score of 7.4 and is fixed in version 13.12.2.
CVSS v3.1
Score 7.4high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The swagger-typescript-api tool, used to generate API clients from OpenAPI specifications, had a vulnerability in versions before 13.12.2. Specifically, the src/resolved-swagger-schema.ts file's getRemoteRequestHeaders function forwarded the --authorizationToken to every URL fetched by fetchRemoteSchemaDocument during the warmUpRemoteSchemasCache process. This behavior allowed an attacker who could supply a malicious OpenAPI spec to cause the developer's or CI's bearer token to be sent to an external, cross-origin endpoint, resulting in exposure of sensitive information. The vulnerability is addressed by updating to version 13.12.2 where this token forwarding behavior is corrected.
Potential Impact
An attacker able to supply a malicious OpenAPI specification can cause the bearer token used for authorization to be leaked to an external endpoint. This exposure compromises confidentiality of sensitive tokens, potentially allowing unauthorized access to protected resources. The vulnerability does not impact integrity or availability directly but poses a significant risk due to token theft.
Mitigation Recommendations
Upgrade swagger-typescript-api to version 13.12.2 or later, where this vulnerability is fixed. There is no indication of alternative mitigations or temporary workarounds. Patch status is not explicitly stated in the vendor advisory, but the description confirms the fix is included in version 13.12.2.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-15T20:16:46.199Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a6a13c09c2644c7f8a6d7f6
Added to database: 07/29/2026, 14:52:48 UTC
Last enriched: 07/29/2026, 15:10:18 UTC
Last updated: 07/29/2026, 15:12:13 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.