CVE-2025-41232: Spring Security authorization bypass for method security annotations on private methods

Quick answers

Is CVE-2025-41232 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-41232 being exploited in the wild.

How severe is CVE-2025-41232?

Low severity, with a CVSS score of 3.1, published 21 May 2025.

Which products and versions are affected?

org.springframework.security:spring-security-aspects (Maven) ECOSYSTEM:introduced=6.4.0,fixed=6.4.6; org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=6.4.0,fixed=6.4.6.

Is there a fix for CVE-2025-41232?

Yes. org.springframework.security:spring-security-aspects (Maven): upgrade to 6.4.6 or later; org.springframework.security:spring-security-core (Maven): upgrade to 6.4.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2025-41232?

Check whether you run org.springframework.security:spring-security-aspects (Maven) or org.springframework.security:spring-security-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

• org.springframework.security:spring-security-aspects (Maven): upgrade to 6.4.6 or later

  # set org.springframework.security:spring-security-aspects to 6.4.6 in your pom.xml or build.gradle

• org.springframework.security:spring-security-core (Maven): upgrade to 6.4.6 or later

  # set org.springframework.security:spring-security-core to 6.4.6 in your pom.xml or build.gradle

Affected products

• org.springframework.security:spring-security-aspects (Maven) ECOSYSTEM:introduced=6.4.0,fixed=6.4.6
• org.springframework.security:spring-security-core (Maven) ECOSYSTEM:introduced=6.4.0,fixed=6.4.6

Identifiers

• CVE-2025-41232
• GHSA-9pp5-9c7g-4r83