Runner file disclosure and SSRF via external refs
Published Aug 31, 2026 · Updated Sep 1, 2026
SSRF and information disclosure in oasdiff-action before 0.0.51 allow remote attackers to access runner resources through pull requests. The action leaves allow-external-refs enabled by default and resolves attacker-controlled HTTP and file $refs on the CI runner. Exposure requires untrusted pull-request specifications, especially fork submissions, and permits requests to internal services or disclosure of readable structured YAML or JSON through action output.
Summary
What happened
SSRF and information disclosure in oasdiff-action before 0.0.51 allow remote attackers to access runner resources through pull requests. The action leaves allow-external-refs enabled by default and resolves attacker-controlled HTTP and file $refs on the CI runner. Exposure requires untrusted pull-request specifications, especially fork submissions, and permits requests to internal services or disclosure of readable structured YAML or JSON through action output.
The record
- CVE
- CVE-2026-53507
- Published
- Aug 31, 2026
- Updated
- Sep 1, 2026
- Vendor
- oasdiff
- Product
- oasdiff-action
- Classifications
- CWE-1188, CWE-200, CWE-918, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 31, 2026CVE publishedPublication date reported by the CVE source.
- Sep 1, 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=< 0.0.51
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