Skip to main content
Mallory
CriticalPublic exploit

Spring Security HTTP Response Headers Omission in Servlet Applications

IdentifiersCVE-2026-22732CWE-693

CVE-2026-22732 is a vulnerability in Spring Security affecting servlet applications that rely on the framework’s lazy (default) writing of configured HTTP response headers. In affected versions, Spring Security may fail to write expected security-related HTTP headers to HTTP responses. The issue affects Spring Security servlet applications in versions 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. The flaw results in omission of configured browser-facing security controls implemented via response headers, weakening the intended protections for downstream clients.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation or exposure to this flaw can cause configured security headers to be absent from servlet responses, reducing browser-enforced protections and weakening application security posture. The provided content indicates this may impact confidentiality and integrity and can expose downstream web clients to attacks such as connection hijacking or sensitive data disclosure through weakened caching or related header-based protections. The primary impact is loss of defense-in-depth controls rather than direct server-side code execution.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by avoiding reliance on lazy/default header writing where feasible and validating that required security headers are consistently present in all servlet responses through testing, reverse-proxy enforcement, or compensating controls. Monitor responses for omission of critical headers and enforce equivalent protections at upstream infrastructure layers where possible. Specific vendor mitigation guidance beyond patching is not available in the provided content.

Remediation

Patch, then assume compromise.

Upgrade Spring Security to a fixed release outside the affected ranges. The vulnerable ranges provided 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. Apply vendor patches in affected downstream products such as SAP Commerce Cloud, SAP Data Hub, Jira Software Data Center/Server, and Jira Service Management Data Center/Server where applicable.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
BroadcomSpring Securityapplication
BroadcomSpring Security Webapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity11

Community discussion across Reddit, Mastodon, and other social sources.