How severe is CVE-2010-3700?

No CVSS score has been assigned to CVE-2010-3700 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-3700?

CVE-2010-3700 affects the following packages: org.springframework.security:spring-security-core (Maven), org.springframework.security:spring-security-core (Maven), org.acegisecurity:acegi-security (Maven). Ecosystems affected: Maven.

How do I fix CVE-2010-3700?

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

How do I detect CVE-2010-3700 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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2010-3700 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.

Is CVE-2010-3700 actively exploited in the wild?

No public exploit code has been indexed for CVE-2010-3700 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-2010-3700?

CVE-2010-3700 has an EPSS (Exploit Prediction Scoring System) score of 1.7%, placing it in the 77th 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.

What type of vulnerability is CVE-2010-3700?

CVE-2010-3700 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2010-3700 published, and has it been updated?

CVE-2010-3700 was published on May 14, 2022 and was last updated on December 5, 2024. 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

CVE-2010-3700 — spring-security-core

CVE-2010-3700 is a CWE-264 vulnerability in org.springframework.security:spring-security-core. A fix is available for org.springframework.security:spring-security-core — see the affected versions and patch details below.

Authentication Bypass Using an Alternate Path or Channel in SpringSource Spring Security and Acegi Security

Published

May 14, 2022

Updated

Dec 5, 2024

Affected

3 pkgs

Patched

2 / 3

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% of all scored CVEsHighest risk

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

Real-World Exposure

3 pkgs affected

☕org.springframework.security:spring-security-core☕org.springframework.security:spring-security-core☕org.acegisecurity:acegi-security

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

VMware SpringSource Spring Security 2.x before 2.0.6 and 3.x before 3.0.4, and Acegi Security 1.0.0 through 1.0.7, as used in IBM WebSphere Application Server (WAS) 6.1 and 7.0, allows remote attackers to bypass security constraints via a path parameter.

Affected Packages

3 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.security:spring-security-core`	≥ 2.0.0&&< 2.0.6	2.0.6`org.springframework.security:spring-security-core:2.0.6`
☕Maven	`org.springframework.security:spring-security-core`	≥ 3.0.0&&< 3.0.4	3.0.4`org.springframework.security:spring-security-core:3.0.4`
☕Maven	`org.acegisecurity:acegi-security`	≥ 1.0.0	No fix

Affected Products

3 products · 20 configurations

Application

acegi-securityacegisecurity

8 versions

1.0.01.0.11.0.21.0.31.0.41.0.51.0.61.0.7

Application

websphere application serveribm

2 versions

6.17.0

Application

springsource spring securityvmware

10 versions

2.0.02.0.12.0.22.0.32.0.42.0.53.0.03.0.13.0.23.0.3

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-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.security:spring-security-core to 2.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-3700 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2010-3700 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2010-3700 — spring-security-core

EPSS Exploitation Probability

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2010-3700 in your dependencies?