Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2021-22112

HIGH

CVE-2021-22112 is a high-severity (CVSS 8.8) vulnerability in org.springframework.security:spring-security-bom. O3 Security confirms whether CVE-2021-22112 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Privilege escalation in spring security

Also known asGHSA-gq28-h5vg-8prx
Published
Feb 23, 2021
Updated
Jul 8, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed

Real-World Exposure

6 pkgs affected
org.springframework.security:spring-security-bomorg.springframework.security:spring-security-bomorg.springframework.security:spring-security-bomorg.springframework.security:spring-security-weborg.springframework.security:spring-security-weborg.springframework.security:spring-security-web

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Spring Security 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, 5.2.x prior to 5.2.9.RELEASE, and older unsupported versions can fail to save the SecurityContext if it is changed more than once in a single request.A malicious user cannot cause the bug to happen (it must be programmed in). However, if the application's intent is to only allow the user to run with elevated privileges in a small portion of the application, the bug can be leveraged to extend those privileges to the rest of the application.

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.springframework.security:spring-security-bom5.4.0&&< 5.4.45.4.4
Mavenorg.springframework.security:spring-security-bom5.3.0&&< 5.3.85.3.8
Mavenorg.springframework.security:spring-security-bomall versions5.2.9
Mavenorg.springframework.security:spring-security-web5.4.0&&< 5.4.45.4.4
Mavenorg.springframework.security:spring-security-web5.3.0&&< 5.3.85.3.8
Mavenorg.springframework.security:spring-security-weball versions5.2.9

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-bom. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.springframework.security:spring-security-bom to 5.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-22112 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2021-22112 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2021-22112. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Spring Security 5.4.x prior to 5.4.4, 5.3.x prior to 5.3.8.RELEASE, 5.2.x prior to 5.2.9.RELEASE, and older unsupported versions can fail to save the SecurityContext if it is changed more than once in a single request.A malicious user cannot cause the bug to happen (it must be programmed in). However, if the application's intent is to only allow the user to run with elevated privileges in a small portion of the application, the bug can be leveraged to extend those privileges to the rest of the application.
O3 Security · Impact-Aware SCA

Is CVE-2021-22112 in your dependencies?

O3 detects CVE-2021-22112 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.