CVE-2023-20860 is a high-severity (CVSS 7.5) vulnerability in org.springframework:spring. A fix is available for org.springframework:spring — see the affected versions and patch details below.
Spring Framework is vulnerable to security bypass via mvcRequestMatcher pattern mismatch
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-2023-20860.
EPSS Exploitation Probability
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-2023-20860 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 378,156 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
org.springframework:spring☕org.springframework:spring☕org.springframework:spring-webmvc☕org.springframework:spring-webmvcReal-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 Framework running version 6.0.0 - 6.0.6 or 5.3.0 - 5.3.25 using "**" as a pattern in Spring Security configuration with the mvcRequestMatcher creates a mismatch in pattern matching between Spring Security and Spring MVC, and the potential for a security bypass.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring | ≥ 6.0.0&&< 6.0.7 | 6.0.7org.springframework:spring:6.0.7 |
| ☕Maven | org.springframework:spring | ≥ 5.3.0&&< 5.3.26 | 5.3.26org.springframework:spring:5.3.26 |
| ☕Maven | org.springframework:spring-webmvc | ≥ 6.0.0&&< 6.0.7 | 6.0.7org.springframework:spring-webmvc:6.0.7 |
| ☕Maven | org.springframework:spring-webmvc | ≥ 5.3.0&&< 5.3.26 | 5.3.26org.springframework:spring-webmvc:5.3.26 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring to 6.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-20860 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-2023-20860 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-20860. 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.
| Product | Fixed in | Advisory |
|---|---|---|
| AMQ Broker 7.10.3 | see advisory | RHSA-2023:3185 |
| OCP-Tools-4.12-RHEL-8 | jenkins-0:2.401.1.1686649641-3.el8 | RHSA-2023:3610 |
| OCP-Tools-4.13-RHEL-8 | jenkins-0:2.401.1.1686680404-3.el8 | RHSA-2023:3622 |
| OpenShift Developer Tools and Services for OCP 4.11 | jenkins-0:2.401.1.1686831596-3.el8 | RHSA-2023:3663 |
| Red Hat Fuse 7.12 | springframework | RHSA-2023:3954 |
| Red Hat OpenShift Container Platform 4.10 | jenkins-0:2.401.1.1685677065-1.el8 | RHSA-2023:3625 |
| Red Hat support for Spring Boot 2.7.13 | springframework | RHSA-2023:4612 |
| Red Hat Virtualization Engine 4.4 | ovirt-dependencies-0:4.5.3-1.el8ev | RHSA-2023:3771 |
Frequently Asked Questions
Is CVE-2023-20860 in your dependencies?
O3 Security finds CVE-2023-20860 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.