SSRF and file reads via ignored reference policy
Published Aug 31, 2026 · Updated Aug 31, 2026
SSRF and local file reads in oasdiff 1.13.2 through 1.18.0 allow context-dependent attackers to access protected resources via untrusted specs. The git-revision branch of load.NewSpecInfo resolves external $ref targets without applying Loader.IsExternalRefsAllowed=false, unlike file and URL paths. Exposure requires explicitly disabling external references and processing an attacker-controlled spec; successful references can fetch internal URLs or readable local files.
Summary
What happened
SSRF and local file reads in oasdiff 1.13.2 through 1.18.0 allow context-dependent attackers to access protected resources via untrusted specs. The git-revision branch of load.NewSpecInfo resolves external $ref targets without applying Loader.IsExternalRefsAllowed=false, unlike file and URL paths. Exposure requires explicitly disabling external references and processing an attacker-controlled spec; successful references can fetch internal URLs or readable local files.
The record
- CVE
- CVE-2026-53508
- Published
- Aug 31, 2026
- Updated
- Aug 31, 2026
- Vendor
- oasdiff
- Product
- oasdiff
- Classifications
- CWE-693, CWE-73, CWE-918, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2026CVE publishedPublication date reported by the CVE source.
- Aug 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.13.2, < 1.18.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo