Medium · published June 11, 2026
Several Spring WS integration paths with Spring Security could surface detailed account state (for example locked or disabled user semantics) to remote SOAP clients through exception messages or callback outcomes, instead of failing with generic authentication errors. That behavior assists remote attackers in distinguishing valid accounts from invalid ones and inferring lifecycle state.
Affected versions:
Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.
| Product | Versions | Fixed in |
|---|---|---|
| broadcom/spring_web_services | < 3.1.9 | 3.1.9 |
| broadcom/spring_web_services | ≥ 4.0.0, < 4.0.19 | 4.0.19 |
| broadcom/spring_web_services | ≥ 4.1.0, < 4.1.3.1 | 4.1.3.1 |
| broadcom/spring_web_services | ≥ 5.0.0, < 5.0.1.1 | 5.0.1.1 |