How to Fix CVE-2026-22753: Spring Security (Bundle Sibling)

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-22753 is a sibling vulnerability in the same vendor advisory as CVE-2026-22746. Applying the patched build named in the primary write-up closes this CVE as well.

What's different about CVE-2026-22753?

Vulnerability in Spring Spring Security. If an application is using securityMatchers(String) and a PathPatternRequestMatcher.Builder bean to prepend a servlet path, matching requests to that filter chain may fail and its related security components will not be exercised as intended by the application. This can lead to the authentication, authorization, and other security controls being rendered inactive on intended requests.This issue affects Spring Security: from 7.0.0 through 7.0.4.

The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.

How to fix CVE-2026-22753

Apply the patched build per the primary write-up: How to Fix CVE-2026-22746.

The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.

Frequently asked questions

Is CVE-2026-22753 fixed by the same patch as CVE-2026-22746?

Yes. CVE-2026-22753 ships in the same vendor advisory as CVE-2026-22746. Applying the patched build named in the primary write-up closes both.

What is the CVSS score for CVE-2026-22753?

The CVSS base score is 7.5 (High).

Is it being exploited?

It is not currently listed in CISA KEV.

References

• Official vendor advisory: https://spring.io/security/cve-2026-22753
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-22753
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-22746

*Part of the Spring Security bundle. Full procedure at CVE-2026-22746.*