Is org.springframework:spring-expression 5.2 vulnerable?
Maven · 26 releases from 5.2.0 to 5.2.25 · latest org.springframework:spring-expression is 7.0.10 · checked 18 Nov 2026
Yes: 5 known advisories
Yes. org.springframework:spring-expression 5.2.25, the last 5.2 release, is affected by 5 known security advisories (2 high, 2 medium, 1 low), including CVE-2026-41849, CVE-2026-41850, CVE-2026-41851. 3 more affect earlier 5.2.x releases. At least one has no fixed release yet.
Is your project on an affected org.springframework:spring-expression?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.springframework:spring-expression 5.2.25
Spring Framework Denial of Service via Integer Overflow in SpEL Expressions
- Affected
- <=5.3.39
- Fixed in
- No fix released
Spring Framework Algorithmic Denial of Service via SpEL Expressions
- Affected
- >=7.0.0 <7.0.8 · >=6.2.0 <6.2.19 · >=6.1.0 <=6.1.21 · <=5.3.39
- Fixed in
- 6.2.19, 7.0.8
Spring Framework Denial of Service via Unbounded Cache in SpEL
- Affected
- >=7.0.0 <7.0.8 · >=6.2.0 <6.2.19 · >=6.1.0 <=6.1.21 · <=5.3.39
- Fixed in
- 6.2.19, 7.0.8
Spring Framework Arbitrary Method Invocation in SpEL Expressions
- Affected
- >=7.0.0 <7.0.8 · >=6.2.0 <6.2.19 · >=6.1.0 <=6.1.21 · <=5.3.39
- Fixed in
- 6.2.19, 7.0.8
Spring Framework vulnerable to Denial of Service
- Affected
- <5.3.39
- Fixed in
- 5.3.39
Fixed within 5.2.x, affecting earlier releases
Spring Framework vulnerable to denial of service
- Affected
- >=6.0.0 <6.0.8 · >=5.3.0 <5.3.27 · <5.2.24.RELEASE
- Fixed in
- 5.2.24.RELEASE, 5.3.27, 6.0.8
Spring Framework vulnerable to denial of service via specially crafted SpEL expression
- Affected
- >=6.0.0 <6.0.7 · >=5.3.0 <5.3.26 · <5.2.23.RELEASE
- Fixed in
- 5.2.23.RELEASE, 5.3.26, 6.0.7
Allocation of Resources Without Limits or Throttling in Spring Framework
- Affected
- >=5.3.0 <5.3.17 · <5.2.20.RELEASE
- Fixed in
- 5.2.20.RELEASE, 5.3.17
Every org.springframework:spring-expression 5.2.x release
Affected: 5.2.0 to 5.2.25. Latest org.springframework:spring-expression: 7.0.10.
| Version | Known advisories |
|---|---|
| org.springframework:spring-expression 5.2.25 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808 |
| org.springframework:spring-expression 5.2.24 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808 |
| org.springframework:spring-expression 5.2.23 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863 |
| org.springframework:spring-expression 5.2.22 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861 |
| org.springframework:spring-expression 5.2.21 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861 |
| org.springframework:spring-expression 5.2.20 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861 |
| org.springframework:spring-expression 5.2.19 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.18 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.17 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.16 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.15 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.14 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.13 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.12 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.11 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.10 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.9 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.8 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.7 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.6 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.5 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.4 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.3 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.2 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.1 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
| org.springframework:spring-expression 5.2.0 | CVE-2026-41849, CVE-2026-41850, CVE-2026-41851, CVE-2026-41852, CVE-2024-38808, CVE-2023-20863, CVE-2023-20861, CVE-2022-22950 |
Which of your client projects are still on org.springframework:spring-expression 5.2?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.springframework:spring-expression version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.springframework:spring-expression versions
- org.springframework:spring-expression 6.1
- org.springframework:spring-expression 6.0
- org.springframework:spring-expression 5.3
- org.springframework:spring-expression 5.1
- org.springframework:spring-expression 5.0
- org.springframework:spring-expression 4.3
- org.springframework:spring-expression 7.0
- org.springframework:spring-expression 6.2
- All org.springframework:spring-expression advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.