Loading vulnerability…
CVE-2026-22732 is a protection-mechanism failure in Spring Security Servlet applications. When an application configures HTTP response headers through Spring Security while using the default lazy header-writing behavior, configured headers may not be written to the servlet response. Affected Spring Security versions are 5.7.0 through 5.7.21, 5.8.0 through 5.8.23, 6.3.0 through 6.3.14, 6.4.0 through 6.4.14, 6.5.0 through 6.5.8, and 7.0.0 through 7.0.3.
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 2 candidates 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.
39 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A critical SAP Commerce Cloud vulnerability mentioned only as one of several previously fixed flaws.
One of several critical SAP NetWeaver vulnerabilities that can expose environments to unauthorized access, memory corruption, data exposure, or service disruption.
A Spring Security vulnerability mentioned only as broader ecosystem background; described here as caching issues.
A Spring Security HTTP caching vulnerability mentioned as background vendor security history.
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.