Loading story…
Broadcom published a large set of Spring security advisories affecting Spring Framework and related projects, with Sonatype tracking 91 CVEs and identifying 209,569 affected software components at the time of publication. The disclosures span multiple vulnerability classes, including insecure deserialization, untrusted code execution under certain conditions, sensitive information exposure, SSRF, path traversal, denial of service, and improper authorization, creating a significant downstream remediation burden for organizations that embed vulnerable Spring components indirectly through other software.
Among the most serious issues, CVE-2026-59285 in Spring for GraphQL was highlighted as a critical unsafe deserialization flaw that can lead to remote code execution in specific scenarios, while CVE-2026-59318 in Spring AI was described as a prompt-injection-related tool-calling boundary bypass that could enable privilege escalation. Spring’s security advisory portal published the vendor notices, and defenders were urged to inventory Spring versions across their environments, determine real exposure and exploitability, and move affected systems to fixed releases as quickly as possible.
See affected versions and whether adversaries are exploiting it.
24 events from the most recent confirmed update back to the earliest known activity.
CVE-2026-59281 can enable reflected XSS through certain HTML-escaped Spring MVC/WebFlux field-error rendering flows; CVE-2026-47886 can cause CPU and heap exhaustion through large-exponent BigDecimal or BigInteger SpEL power operations; and CVE-2026-59280 can permit path traversal in Spring FreeMarker integrations when view names derive from untrusted input. Tenable Nessus plugin 341189 identifies affected Spring Framework versions using self-reported version information rather than active exploitation testing.
CVE-2026-47892, an incorrect-authorization vulnerability in Spring Framework, was published and patched on August 20, 2026. The flaw is network-reachable without privileges or user interaction and has high integrity impact; Tenable Nessus plugin 341188 detects affected installed Spring Framework versions on Windows, macOS, and Unix.
Tenable published Nessus plugin 341190 to detect Spring Framework CVE-2026-47883, CVE-2026-47889, and CVE-2026-47890 on Windows, macOS, and Unix installations. The plugin rates CVE-2026-47890 as network-reachable and unauthenticated with high confidentiality, integrity, and availability impact under CVSS v3.
CVE-2026-47888 was published and patched in Spring Framework on August 20, 2026. The CWE-401 improper-memory-release flaw is remotely exploitable without authentication or user interaction and can cause denial of service with high availability impact; Tenable's spring_framework_CVE-2026-47888.nasl detects affected installations.
CVE-2026-47885 was published and patched in Spring Framework. The CWE-770 flaw is remotely exploitable without authentication or user interaction and affects Spring Framework versions before 6.1.29, 6.2.20, and 7.0.x fixed releases; Tenable's plugin 341187 detects affected installations.
Sonatype tracked 91 CVEs across Spring Framework and related projects in the August 20, 2026 disclosure event. The affected projects included Spring Security, Spring Cloud Config, Spring AI, Spring Data REST, Spring Integration, Reactor Core, Reactor Netty, Spring AMQP, and Spring Batch.
On August 20, 2026, Broadcom published a large batch of Spring security advisories spanning Spring Framework and related projects. The disclosures covered issues such as insecure deserialization, code execution conditions, sensitive information exposure, SSRF, path traversal, denial of service, and improper authorization.
During the week of August 17, 2026, Spring Integration 7.2.0 and Spring AMQP 4.2.0 addressed four vulnerabilities: Java-deserialization RCE and JSR-223 scripting-engine concurrency flaws in Spring Integration, plus compressed-message denial of service and clear-text RabbitMQ administrator-password exposure in Spring AMQP.
CVE-2026-47835 was published and patched in Spring AI Vector Store components after special characters could force arbitrary queries against Elasticsearch, OpenSearch, and GemFire VectorDB. The issue affects the spring-ai-elasticsearch-store, spring-ai-opensearch-store, and spring-ai-gemfire-store artifacts; fixed releases are Spring AI 1.0.9 and 1.1.8.
CVE-2026-40986 was published and patched in Spring Web Flow after JavaScript RemotingHandler could render error-response bodies as HTML despite a non-HTML content type, enabling reflected attacker-controlled error details to execute as script in a user's browser. The issue affected versions 4.0.0, 3.0.0 through 3.0.1, and 2.5.0 through 2.5.1; updating spring-webflow and related packages to 3.0.2 or later remediates it.
CVE-2026-40985 was published and patched in Spring Web Flow. Applications using WebFlowELExpressionParser could process malicious Unified EL expressions; affected users were advised to update org.springframework.webflow:spring-webflow and related packages to version 3.0.2 or later.
CVE-2026-40995 was published and patched in Spring Web Services' spring-ws-security library. X509AuthenticationProvider could authenticate a certificate-mapped user without enforcing disabled, locked, expired, or credentials-expired account checks; upgrading to version 4.1.4 or later remediates the issue.
CVE-2026-40996 was published and patched in Spring Web Services' spring-ws-security library. The Wss4jSecurityInterceptor enabled RSA PKCS#1 v1.5 key transport by default, allowing inbound WS-Security decryption to accept rsa-1_5 encrypted key material unless reconfigured; upgrading to version 4.1.4 or later remediates the issue.
CVE-2026-40994 was published and patched in Spring Web Services' spring-ws-security library. Incorrect initialization in Wss4jSecurityInterceptor could disable inbound WSS4J WS-I Basic Security Profile enforcement, allowing network services to accept WS-Security messages that violate BSP rules; upgrading to version 4.1.4 or later remediates it.
CVE-2026-41000 was published and patched in Spring Web Services' spring-ws-security library. The flaw could prevent configured WSS4J replay-cache protections from being applied during validation for UsernameToken, Timestamp, and certain SAML checks; upgrading to version 4.1.4 or later remediates it.
CVE-2026-40992 was published and patched in Spring Boot Mail auto-configuration, where hostname verification was not enabled by default. The issue affected Spring Boot 4.0.0 through 4.0.6, 3.5.0 through 3.5.14, and 3.4.0 through 3.4.16; updating spring-boot-starter-mail and related packages to 3.5.15 or later remediates it.
CVE-2026-41001 was published and patched in Spring Boot's ArtemisEmbeddedConfigurationFactory. When an embedded Artemis broker lacks an explicitly configured data path, a local attacker could pre-create or symlink its predictable directory; affected users were advised to update spring-boot-autoconfigure and related packages to version 3.5.15 or later.
CVE-2026-41699 was published and patched in Spring for GraphQL. The unsafe-deserialization flaw can enable remote code execution through malicious paginated GraphQL requests when a vulnerable application exposes a Connection field and has usable deserialization classes on its classpath; updating to version 1.4.6 or later remediates it.
CVE-2026-41856 was published and patched in Spring for GraphQL. The flaw can cause authorization annotations on @Controller data-fetcher methods to be ignored in affected type hierarchies; updating spring-graphql and related packages to version 1.4.6 or later remediates it.
CVE-2026-41854 was published and patched in Spring Framework after incorrect host parsing in UriComponentsBuilder could enable SSRF when applications use it to parse and validate externally supplied URLs. The issue affected Spring Framework 7.0.0 through 7.0.7 and 6.2.0 through 6.2.18; updating spring-web and related packages to 6.2.19 or later remediates it.
Broadcom said its June 2026 Spring security release was the largest set of Spring security updates in the project's 23-year history, reflecting the growing volume of discovered flaws.
In April 2026, Spring received 482 security reports across 65 scanned projects. Broadcom said 370 of those reports came from Spring's own scanning capabilities and 112 were submitted by the community.
Broadcom reported that Spring received 55 security reports in March 2026, part of a sharp rise in vulnerability findings affecting the ecosystem.
At the time of publication, Sonatype Guide identified 209,569 affected software components tied to the Spring vulnerabilities, including many non-Spring packages that bundle vulnerable Spring code. This highlighted the downstream remediation impact of the disclosure.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
27 references tracked. Mallory keeps watching after this page renders.
tenable.com
Open sourcetenable.com
Open sourcetenable.com
Open sourcetenable.com
Open sourcecwe.mitre.org
Open sourcecwe.mitre.org
Open sourcecwe.mitre.org
Open sourcespring.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Spring disclosed and national cyber agencies amplified six vulnerabilities in **Spring Tools** that affect developer environments for the Spring Java ecosystem, including **Spring Tools for Eclipse 5.2.0 and earlier** and **Spring Tools for VSCode, Cursor, and Theia 2.2.0 and earlier**. The most serious issues include **`CVE-2026-47858`**, which can expose Spring Boot applications started with live information mode to **JMX-based remote code execution**, and **`CVE-2026-47873`**, where the Boot Dashboard Docker integration publishes unauthenticated **JDWP** and **JMX** ports on **`0.0.0.0`** instead of limiting access to loopback, potentially exposing container control interfaces to the network. A third high-severity flaw, **`CVE-2026-47882`**, weakens Spring Boot DevTools remote restart authentication by generating the shared secret with a non-cryptographic pseudo-random number generator. Advisories also cited additional issues involving **plaintext logging of proxy credentials**, **cleartext storage of remote secrets**, and a **cross-site scripting** vulnerability. Italy's ACN and the Canadian Centre for Cyber Security said updates are available or pending through Spring security bulletins, with fixed versions identified as **Spring Tools for Eclipse 5.3.0** and **Spring Tools for VSCode, Cursor, and Theia 2.3.0**, and urged organizations to upgrade affected tooling.
Jul 30, 2026
Spring published three security advisories covering **Spring AI** and **Spring gRPC**, including `CVE-2026-40967`, a flaw in VectorStore `FilterExpressionConverter` implementations that can let attackers manipulate generated vector store queries because keys and values are not properly escaped. The issue affects Spring AI versions `1.0.0` through `1.0.5` and `1.1.0` through `1.1.4`, and is fixed in `1.0.6` and `1.1.5`. External vulnerability tracking describes the bug as a high-severity code or query injection risk with CVSS `AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L` and maps it to `CWE-94`. Spring also disclosed two **Spring gRPC** vulnerabilities: `CVE-2026-40968`, in which `SecurityContext` data can leak across requests after an authorization failure, and `CVE-2026-40969`, where an `AuthenticationException` message may be reflected back to a remote client. Together, the advisories point to risks of query manipulation, cross-request security context exposure, and unintended error-message disclosure in applications built on affected Spring components.
Jun 29, 2026
Spring disclosed a broad set of vulnerabilities across **Spring Framework**, **Spring Data Commons**, and **Spring LDAP**, including a high-severity authentication bypass tracked as `CVE-2026-41720`. The LDAP flaw allows login with a valid username and an empty or null password when the backing LDAP server permits unauthenticated binds, affecting authentication flows that use `AbstractContextSource`, `LdapTemplate`, or `LdapClient`. Spring also fixed a low-severity WebFlux session fixation issue (`CVE-2026-41839`) tied to compromised subdomains, and an information disclosure bug (`CVE-2026-41841`) in Spring MVC and WebFlux where shared static-resource caches could expose protected files if a public resource with the same name had already been cached. Several denial-of-service issues were patched at the same time. In Spring Framework, `CVE-2026-41840` can leak memory through malicious multipart requests in WebFlux, while `CVE-2026-41842` can tie up HTTP connections through slow resolution of versioned file-system resources in Spring MVC or WebFlux. In Spring Data Commons, `CVE-2026-41695`, `CVE-2026-41711`, `CVE-2026-41716`, and `CVE-2026-41721` can be triggered by attacker-controlled property paths, sort parameters, property names, or `@ProjectedPayload` data binding, leading to stack overflows, heap exhaustion, or excessive memory allocation when applications expose those inputs to untrusted users. Spring urged customers to upgrade to fixed releases, including Framework `7.0.8`, `6.2.19`, and `6.1.28`, Data Commons `4.0.6` and `3.5.12`, and LDAP `2.4.5`, `3.2.18`, `3.3.8`, or `4.0.4`, with some older branches receiving fixes only through commercial support.
Jun 29, 2026