Only one of the 91 vulnerabilities Spring patched is rated critical
Spring has patched 91 vulnerabilities spread across a range of subprojects, according to SecurityWeek. The advisories on spring.io are dated 20 August. Spring itself rates one of them critical, and it concerns the embedded LDAP server in Spring Security, where an attacker who can reach the listener port is able to authenticate with a well-known administrative bind DN and then read or modify entries in the directory. More than a dozen of the remaining flaws carry a high severity rating. Security firm Sonatype analyzed the patches and found that they affect more than 200,000 software components, as reported by SecurityWeek.
What happens technically
Spring is an open source application framework for the Java platform. SecurityWeek describes it as a framework that simplifies the creation of enterprise applications through dependency injection, aspect oriented programming and modular support for web, data and messaging architectures. It sat under VMware for years and now belongs to Broadcom. The advisory listing on spring.io shows that the 20 August fixes are spread across a large number of subprojects, among them Spring Security, Spring Data JPA, Spring Cloud Config, Reactor Netty, Spring Data REST, Spring Integration, Spring AI, Spring AMQP, Reactor Core and Spring Batch. SecurityWeek states that more than 200 vulnerabilities have been patched in Spring so far this year, against 16 in 2025 and 22 in 2024, and attributes the surge to Broadcom's use of AI.
The critical flaw is CVE-2026-59270. The Spring advisory explains that the embedded UnboundID LDAP server in Spring Security, the UnboundIdContainer class, unconditionally registers an administrative credential and binds its listener to all available network interfaces. Two preconditions must hold. The application must actually use UnboundIdContainer, either configured directly or through Spring Boot auto configuration with the properties beginning with spring.ldap.embedded. The listener port must also be reachable from the attacker's network position, meaning it is not restricted to localhost by an external firewall or network policy. When both hold, the attacker can authenticate with the well-known administrative bind DN and read or modify entries in the directory, which lives in memory. The advisory points to a CVSS vector describing a network attack of low complexity that requires no privileges and no user interaction. Spring lists open source fixes in Spring Security 7.1.1 and 7.0.7. The remaining fixed releases, namely 7.1.0.1, 7.0.6.1, 6.5.12, 6.4.19, 5.8.28 and 5.7.26, are marked Enterprise Support Only. Four of the six affected branches therefore have no freely available fix in the advisory.
The second flaw singled out, CVE-2026-59285, sits in Spring for GraphQL. The sources disagree on how severe it is. Spring rates it high, while Sonatype, as reported by SecurityWeek, calls it a critical remote code execution issue. The advisory sets out four conditions that must all be true. The application must use Spring GraphQL, it must use Jackson 2.x for JSON deserialization, it must expose a paginated Connection field, and its classpath must contain specific classes that can be leveraged to execute unintended logic during instantiation or deserialization. When all four are met, an attacker can craft a GraphQL request that leads to remote code execution. Spring points to CWE-502, the category for unsafe deserialization. Affected releases are Spring for GraphQL 2.0.0 through 2.0.4, and 2.0.5 is the open source fix. SecurityWeek also mentions CVE-2026-59318, a medium severity issue in Spring AI's tool calling functionality. According to Sonatype it can allow privilege escalation through instructions smuggled into the text the language model reads.
What this means for you if you own Java applications
If your teams build software on Java, there is a good chance Spring already sits somewhere in your dependency tree without anyone having chosen it deliberately. Sonatype's figure of more than 200,000 affected software components says something about how widely the framework is spread. Our assessment is that the most important job this week is not upgrading Spring, but finding out where Spring actually lives in your estate. A build tool such as Maven or Gradle pulls in the dependencies of its dependencies, and that is general knowledge about such tools rather than something the advisories say. The consequence is still concrete for you. A library you have never heard of may have carried a Spring component into your product, and then you have it without having decided to.
At the same time it is worth keeping a cool head about the severity. Only one of the 91 is rated critical, and it assumes that your application really does run the embedded LDAP server and that the port is reachable from outside. If you do not run UnboundIdContainer, the critical flaw does not apply to you. Two points are still worth carrying forward. The first is that four of the six affected Spring Security branches only receive the fix through a paid support agreement, which makes the upgrade a budget question as much as a technical one. The second is that Spring and Sonatype disagree about the GraphQL flaw, with Spring saying high and Sonatype saying critical. When the label is contested, your own configuration decides, and somebody has to check whether the advisory's conditions are actually met in your environment.
Berigo recommends
- Map where Spring exists in your estate, both as a direct dependency and as a dependency of something else. Use the dependency report from your build tool rather than what your developers remember.
- Check whether any of your applications run the embedded UnboundID directory from Spring Security. If the answer is yes, treat CVE-2026-59270 as urgent.
- Establish which Spring Security branch you are on, and confirm whether your fix requires a paid support agreement before you plan the upgrade.
- Walk through the four conditions in the CVE-2026-59285 advisory against your own GraphQL services. Do not rely on the severity label alone when the sources disagree.
- Ask your suppliers to confirm in writing whether the products they deliver contain the affected Spring components, and when the fixes will arrive.
Security that is understood, governed and works.
Let us help you turn security into an advantage, not a cost. Get in touch for a no-obligation conversation about where your organisation stands and what to prioritise first.
Get in touch