CVE-2018-1260 — spring-security-oauth2
CRITICALCVE-2018-1260 is a critical-severity (CVSS 9.8) Code Injection vulnerability in org.springframework.security.oauth:spring-security-oauth2. EPSS puts its 30-day exploitation probability at 10.6% (96th percentile). A fix is available for org.springframework.security.oauth:spring-security-oauth2 — see the affected versions and patch details below.
Spring Security OAuth vulnerable to remote code execution (RCE)
EPSS Exploitation Probability
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
org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth2☕org.springframework.security.oauth:spring-security-oauth2Real-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 OAuth, versions 2.3 prior to 2.3.3, 2.2 prior to 2.2.2, 2.1 prior to 2.1.2, 2.0 prior to 2.0.15 and older unsupported versions contains a remote code execution vulnerability. A malicious user or attacker can craft an authorization request to the authorization endpoint that can lead to remote code execution when the resource owner is forwarded to the approval endpoint.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.3.0&&< 2.3.3 | 2.3.3org.springframework.security.oauth:spring-security-oauth2:2.3.3 |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.2.0&&< 2.2.2 | 2.2.2org.springframework.security.oauth:spring-security-oauth2:2.2.2 |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.1.0&&< 2.1.2 | 2.1.2org.springframework.security.oauth:spring-security-oauth2:2.1.2 |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 2.0.0&&< 2.0.15 | 2.0.15org.springframework.security.oauth:spring-security-oauth2:2.0.15 |
| ☕Maven | org.springframework.security.oauth:spring-security-oauth2 | ≥ 1.0.0 | No fix |
Affected Products
spring security oauthpivotal_softwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security.oauth:spring-security-oauth2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.security.oauth:spring-security-oauth2 to 2.3.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1260 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
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.
Frequently Asked Questions
Is CVE-2018-1260 in your dependencies?
Find it across Maven, including transitive dependencies.