Spring Security authorization bypass for method security annotations on private methods

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS

• CVE-2025-41232: 0.62% estimated exploitation activity in the next 30 days; percentile 49.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Spring Security Aspects may not correctly locate method security annotations on private methods. This can cause an authorization bypass. Your application may be affected by this if the following are true: You are using @EnableMethodSecurity(mode=ASPECTJ) and spring-security-aspects, and You have Spring Security method annotations on a private method In that case, the target method may be able to be invoked without proper authorization. You are not affected if: You are not using @EnableMethodSecurity(mode=ASPECTJ) or spring-security-aspects, or You have no Spring Security-annotated private methods

Published by the source

21 May 2025, 15:30 UTC

Last modified by the source

15 Oct 2025, 20:13 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9pp5-9c7g-4r83

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-41232

Advisory: Spring Security authorization bypass for method security annotations on private methods
IDs: CVE-2025-41232, GHSA-9pp5-9c7g-4r83
Record: https://patchnext.com/advisories/cve-2025-41232 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.springframework.security:spring-security-core 6.4.6; org.springframework.security:spring-security-aspects 6.4.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework.security:spring-security-core: affected >= 6.4.0, < 6.4.6; fixed in 6.4.6
- Maven org.springframework.security:spring-security-aspects: affected >= 6.4.0, < 6.4.6; fixed in 6.4.6

## Suggested inspection (read-only)
- Maven org.springframework.security:spring-security-core: check the installed version with your package manager.
- Maven org.springframework.security:spring-security-aspects: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.springframework.security:spring-security-core, org.springframework.security:spring-security-aspects.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-9pp5-9c7g-4r83 (GitHub-reviewed advisory GHSA-9pp5-9c7g-4r83 lists affected ranges: Maven org.springframework.security:spring-security-aspects >=6.4.0 =6.4.0 <6.4.6)

Commands are suggestions: review each one before running it.