CVE-2026-59903 affects the HTTP CORS handler in Netty's io.netty:netty-codec-http component before the fixed releases 4.1.137.Final and 4.2.17.Final. CorsHandler.setVaryHeader replaces application-defined Vary headers, including Authorization or Cookie, with Origin instead of preserving the existing cache-variation requirements. In applications behind caching proxies or CDNs, this can cause authenticated or user-specific responses to be reused across users, resulting in cache poisoning and disclosure of sensitive information.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity information-disclosure vulnerability in Netty's HTTP codec. CorsHandler overwrites application Vary headers with Origin, potentially causing caching proxies or CDNs to serve authenticated responses to other users. The reported CVSS v3 base score is 7.5. Fixes are available in versions 4.1.137.Final and 4.2.17.Final.
Unknown
A medium-severity Netty HTTP CORS handler flaw in which CorsHandler's setVaryHeader can overwrite application Vary headers with Origin, potentially allowing caching proxies or CDNs to serve authenticated responses to other users and disclose sensitive data.
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.