How severe is CVE-2022-31690?

CVE-2022-31690 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-31690?

CVE-2022-31690 affects the following packages: org.springframework.security:spring-security-oauth2-client (Maven), org.springframework.security:spring-security-oauth2-client (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-31690?

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.

How do I detect CVE-2022-31690 in my Maven dependencies?

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.

How do I mitigate CVE-2022-31690 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2022-31690?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-31690 can be triaged on real exposure rather than presence alone.

Is CVE-2022-31690 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-31690 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-31690?

CVE-2022-31690 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2022-31690 published, and has it been updated?

CVE-2022-31690 was published on October 31, 2022 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ 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

Oct 31, 2022

Updated

Aug 12, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Sep 18, 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.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2022-31690 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.security:spring-security-oauth2-client`	≥ 5.7.0&&< 5.7.5	5.7.5`org.springframework.security:spring-security-oauth2-client:5.7.5`
☕Maven	`org.springframework.security:spring-security-oauth2-client`	all versions	5.6.9`org.springframework.security:spring-security-oauth2-client:5.6.9`

Detection & mitigation playbook

Open-source dependency

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.
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.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-31690 can be triaged on real exposure rather than presence alone.

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

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.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-31690 in your dependencies?

O3 Security finds CVE-2022-31690 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works