GHSA-2jcc-mxv7-p3f9: oasdiff does not enforce --allow-external-refs=false on the git-revision load path (SSRF / local file read)
From versions 1.13.2 through 1.18.0, the oasdiff tool did not enforce the --allow-external-refs=false setting when loading OpenAPI specs from a git revision path. This flaw allowed external references to be resolved even when explicitly disabled, exposing users to server-side request forgery (SSRF) and local file read risks via crafted $ref values. The issue affects CLI commands and Go library consumers using the git-revision load path with external refs disabled. Version 1.18.1 fixes this by enforcing the external refs policy on the git-revision path and returning a dedicated exit code when external refs are blocked.
AI Analysis
Technical Summary
oasdiff versions 1.13.2 through 1.18.0 contain a vulnerability where the --allow-external-refs=false setting is not enforced on the git-revision load path (e.g., refs like main:openapi.yaml). This allows external $ref resolution despite the setting being disabled, leading to potential SSRF and local file read exposures when processing untrusted OpenAPI specs. The file and URL load paths correctly enforce the setting; only the git-revision path is affected. The vulnerability was introduced in version 1.13.2 and fixed in 1.18.1, which enforces the policy and returns exit code 123 on refusal of external refs.
Potential Impact
Users who disable external references to safely process untrusted OpenAPI specifications remain exposed to SSRF attacks and local file reads when loading specs via the git-revision path. This could allow an attacker to cause the tool to fetch internal network resources or read local files, potentially leaking sensitive information. The impact is limited to scenarios where external refs are disabled but specs are loaded from git revisions. Users with default settings (allow-external-refs=true) are not affected by this specific issue.
Mitigation Recommendations
Upgrade to oasdiff version 1.18.1 or later, which enforces the --allow-external-refs=false setting on the git-revision load path and returns a dedicated exit code when external refs are blocked. Alternatively, avoid using the git-revision input form when processing untrusted specs with external refs disabled. Patch status is official-fix in version 1.18.1.
GHSA-2jcc-mxv7-p3f9: oasdiff does not enforce --allow-external-refs=false on the git-revision load path (SSRF / local file read)
Description
From versions 1.13.2 through 1.18.0, the oasdiff tool did not enforce the --allow-external-refs=false setting when loading OpenAPI specs from a git revision path. This flaw allowed external references to be resolved even when explicitly disabled, exposing users to server-side request forgery (SSRF) and local file read risks via crafted $ref values. The issue affects CLI commands and Go library consumers using the git-revision load path with external refs disabled. Version 1.18.1 fixes this by enforcing the external refs policy on the git-revision path and returning a dedicated exit code when external refs are blocked.
CVSS v4.0
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
oasdiff versions 1.13.2 through 1.18.0 contain a vulnerability where the --allow-external-refs=false setting is not enforced on the git-revision load path (e.g., refs like main:openapi.yaml). This allows external $ref resolution despite the setting being disabled, leading to potential SSRF and local file read exposures when processing untrusted OpenAPI specs. The file and URL load paths correctly enforce the setting; only the git-revision path is affected. The vulnerability was introduced in version 1.13.2 and fixed in 1.18.1, which enforces the policy and returns exit code 123 on refusal of external refs.
Potential Impact
Users who disable external references to safely process untrusted OpenAPI specifications remain exposed to SSRF attacks and local file reads when loading specs via the git-revision path. This could allow an attacker to cause the tool to fetch internal network resources or read local files, potentially leaking sensitive information. The impact is limited to scenarios where external refs are disabled but specs are loaded from git revisions. Users with default settings (allow-external-refs=true) are not affected by this specific issue.
Mitigation Recommendations
Upgrade to oasdiff version 1.18.1 or later, which enforces the --allow-external-refs=false setting on the git-revision load path and returns a dedicated exit code when external refs are blocked. Alternatively, avoid using the git-revision input form when processing untrusted specs with external refs disabled. Patch status is official-fix in version 1.18.1.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2jcc-mxv7-p3f9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53508"]
- Ecosystems
- ["Go"]
- Database Specific Severity
- MODERATE
- Cvss Version
- 4.0
Threat ID: 6a4e4ee6c9d9e3dbe32899cd
Added to database: 07/08/2026, 13:21:42 UTC
Last enriched: 07/08/2026, 13:39:03 UTC
Last updated: 07/08/2026, 13:39:03 UTC
Views: 2
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.