NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2022-31690 — spring-security-oauth2-cl…

HIGH

CVE-2022-31690 is a high-severity (CVSS 8.1) vulnerability in org.springframework.security:spring-security-oauth2-client. A fix is available for org.springframework.security:spring-security-oauth2-client — see the affected versions and patch details below.

spring-security-oauth2-client vulnerable to Privilege Escalation

Also known asGHSA-32vj-v39g-jh23
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31690.

EPSS Exploitation Probability

via FIRST.org ↗
1.3%probability of exploitation in next 30 days
Lower Risk+0.17%
Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk
0.00%0.58%1.17%1.75%0.3%1.3%Apr 26Aug 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
☕org.springframework.security:spring-security-oauth2-client☕org.springframework.security:spring-security-oauth2-client

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, versions 5.7 prior to 5.7.5, and 5.6 prior to 5.6.9, and older unsupported versions could be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can modify a request initiated by the Client (via the browser) to the Authorization Server which can lead to a privilege escalation on the subsequent approval. This scenario can happen if the Authorization Server responds with an OAuth2 Access Token Response containing an empty scope list (per RFC 6749, Section 5.1) on the subsequent request to the token endpoint to obtain the access token.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.security:spring-security-oauth2-client≥ 5.7.0&&< 5.7.55.7.5org.springframework.security:spring-security-oauth2-client:5.7.5
☕Mavenorg.springframework.security:spring-security-oauth2-clientall versions5.6.9org.springframework.security:spring-security-oauth2-client:5.6.9

Affected Products

2 products · 4 configurations
Application
active iq unified managernetapp
all
Application
spring securityvmware
≥ 5.7.0 && < 5.7.5
range

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-oauth2-client, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

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

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat Integration Camel-K, Camel-Quarkus, and Camel-SpringBoot do not directly use or ship the affected software, but do have references to it in their Maven POMs. As such their impact has been reduced to Low.

ProductFixed inAdvisory
Migration Toolkit for Runtimes 1 on RHEL 8org.keycloak-keycloak-spring-security-adapterRHSA-2023:1285
Migration Toolkit for Runtimes 1 on RHEL 8mtr/mtr-web-container-rhel8:1.0-22RHSA-2023:1286
MTA-6.1-RHEL-8mta/mta-windup-addon-rhel8:6.1.0-11RHSA-2023:2041
Red Hat OpenShift Container Platform 4.10jenkins-0:2.387.1.1680701869-1.el8RHSA-2023:1655

Frequently Asked Questions

Spring Security, versions 5.7 prior to 5.7.5, and 5.6 prior to 5.6.9, and older unsupported versions could be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can modify a request initiated by the Client (via the browser) to the Authorization Server which can lead to a privilege escalation on the subsequent approval. This scenario can happen if the Authorization Server responds with an OAuth2 Access Token Response containing an empty scope list (per RFC 6749, Section 5.1) on the subsequent request to the token endpoint to obtain the access token.
O3 Security · Impact-Aware SCA

Is CVE-2022-31690 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-31690: spring-security-oauth2 — Fixed in 5.7.5