CVE-2026-53508 affects github.com/oasdiff/oasdiff. The vulnerability is a policy-enforcement bypass in the git-revision input/load path (rev:path): oasdiff does not correctly enforce the --allow-external-refs=false setting when loading OpenAPI specifications through that path. As a result, external $ref targets can still be resolved even though external references were explicitly disabled. In practice, when oasdiff processes an untrusted OpenAPI document via the git-revision load path, an attacker can embed external $ref values pointing to HTTP(S) resources or local filesystem paths, including file:// URIs, and cause the tool to dereference them. This creates an SSRF and local file read condition despite the intended safeguard.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.