CVE-2026-67354 is an information disclosure vulnerability in guzzlehttp/guzzle versions prior to 7.15.1. The issue resides in RedirectMiddleware when the optional allow_redirects.referer setting is enabled. During same-scheme redirects, such as HTTPS-to-HTTPS, the middleware generates a Referer header for the follow-up request and incorrectly includes the URI fragment from the original request. Because URI fragments commonly carry client-side secrets such as one-time login values, access tokens, or state parameters, a redirect target controlled by an attacker can receive sensitive data that should never be transmitted in HTTP headers. Version 7.15.1 corrects this behavior by stripping the fragment before constructing the Referer value.
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.
9 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.