Spring MVC and WebFlux applications are vulnerable to Denial of Service (DoS) attacks when resolving static resources.
Affected versions:
Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.
Spring MVC and WebFlux applications are vulnerable to Information Disclosure attacks when resolving static resources.
Affected versions:
Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.
Spring WebFlux applications are vulnerable to Denial of Service (DoS) attacks when processing multipart requests.
Affected versions: Spring Framework 7.0.0 through 7.0.7, 6.2.0 through 6.2.18, 6.1.0 through 6.1.27, 5.3.0 through 5.3.48.
A WebFlux application with a compromised subdomain (for example, compromised via cross-site scripting (XSS)) is vulnerable to an escalation attack exchanging a known session ID for that of an authenticated user.
Affected versions:
Spring Framework 7.0.0 through 7.0.7; 6.2.0 through 6.2.18; 6.1.0 through 6.1.27; 5.3.0 through 5.3.48.
Spring Framework versions 5.3.0 through 5.3.48, 6.1.0 through 6.1.27, 6.2.0 through 6.2.18, and 7.0.0 through 7.0.7 have a vulnerability where WebSocket session IDs are not cryptographically unpredictable. This weakness could potentially be exploited if combined with inadequate authorization controls. The vulnerability is identified as CWE-330 and has a medium severity with a CVSS score of 4.8.
CVE-2026-41720 is a high-severity vulnerability in Spring LDAP where certain DirContextAuthenticationStrategy implementations improperly accept bind requests with a non-empty username and an empty or null password. This affects multiple versions of Spring LDAP, specifically 2.4.0 through 2.4.4, 3.2.0 through 3.2.17, 3.3.0 through 3.3.7, and 4.0.0 through 4.0.3. The vulnerability relates to improper authentication (CWE-287) and could allow unauthorized access if exploited.
CVE-2026-41715 is a medium severity vulnerability in Spring Reactor Netty HTTP client where credentials may be leaked during HTTP redirects from secure to insecure endpoints if the client is configured to follow redirects. This affects versions 1.0.0 through 1.0.51, 1.1.0 through 1.1.35, 1.2.0 through 1.2.17, and 1.3.0 through 1.3.5. No official patch or remediation guidance is currently available.
CVE-2026-41710 is a resource exhaustion vulnerability in Spring Retry affecting versions 1.3.0 through 1.3.4 and 2.0.0 through 2.0.12. An attacker can send many unique requests that cause failures, filling the application-wide stateful retry cache. Once full, the cache rejects further updates, causing all subsequent stateful retries and circuit breakers to fail, impacting application availability. The vulnerability has a medium severity with a CVSS score of 5.9.
In Micrometer, it is possible for a user to provide specially crafted HTTP requests that may cause a denial-of-service (DoS) condition.
Affected versions:
micrometer-core 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18; 1.9.0 through 1.9.17.
micrometer-jetty11 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18.
micrometer-jetty12 1.16.0 through 1.16.5; 1.15.0 through 1.15.11; 1.14.0 through 1.14.15; 1.13.0 through 1.13.18.
In Micrometer, it is possible for a user to provide specially crafted gRPC requests that may cause a denial-of-service (DoS) condition.
Affected versions:
Micrometer 1.16.0 through 1.16.5; 1.15.0 through 1.15.11.
CVE-2026-40990 is a medium severity vulnerability in Spring Cloud Function that allows an attacker to cause an out-of-memory (OOM) error by adding an unlimited number of functions to the Function Registry. This results from allocation of resources without limits or throttling. The vulnerability can lead to denial of service through resource exhaustion but does not affect confidentiality or cause data loss. Multiple specific versions of Spring Cloud Function are affected. No official patch or remediation guidance has been confirmed yet.
CVE-2026-40989 is a medium severity vulnerability in Spring Cloud Function involving uncontrolled recursion in the routing layer. This flaw can cause an out-of-memory (OOM) condition, resulting in denial of service. It does not affect confidentiality but impacts availability due to resource exhaustion. The vulnerability affects specific versions of Spring Cloud Function. No official patch or remediation guidance is currently confirmed.
mcp-security provides Security and Authorization support for Model Context Protocol in Spring AI. Prior to 0.1.9, the mcp-security framework fails to implement the mandatory SSRF mitigations outlined in the Model Context Protocol (MCP) security specifications. Specifically, it processes untrusted URLs for OAuth-related discovery and metadata without verifying if the targets are malicious or internal to the network. This only affects installations with Dynamic Client Registration (DCR) enabled This vulnerability is fixed in 0.1.9.
CVE-2026-41863 is a path traversal vulnerability in Spring AI version 1.1.0. It occurs because the product uses unsanitized, LLM-influenced filenames in Path.resolve before writing files to disk, allowing an attacker with limited privileges to write files outside the intended directory. This could lead to unauthorized file modification or creation in restricted directories. The vulnerability has a medium severity with a CVSS score of 6.5. No official patch or remediation guidance is currently available from the vendor.
The LJ comments import: reloaded plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via PHP_SELF Parameter in all versions up to, and including, 0.97.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The vulnerability arises specifically because PHP_SELF includes attacker-controllable PATH_INFO appended to the script name, and there are two distinct unsanitized echo points for this value in the same function.
Spring Cloud AWS versions from 3.0.0 up to 4.0.1 did not verify the signature of incoming SNS messages on HTTP/HTTPS endpoints using specific notification mapping annotations. This allowed an unauthenticated attacker who knows the endpoint URL to send crafted HTTP POST requests mimicking SNS Notification or SubscriptionConfirmation messages. The vulnerability is fixed in version 4.0.2.
Spring AI's MilvusVectorStore#doDelete(List) implementation is vulnerable to filter-expression injection via unsanitized document IDs.
Spring AI 1.0.x: affected from 1.0.0 through latest 1.0.x; upgrade to 1.0.7 or greater. Spring AI 1.1.x: affected from 1.1.0 through latest 1.1.x; upgrade to 1.1.6 or greater.
When using Google Secrets Manager as a backend for the Spring Cloud Config server a client can craft a request to the config server potentially exposing secrets from unintended GCP projects.
Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); upgrade to 3.1.14 or greater (Enterprise Support Only). Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); upgrade to 4.1.10 or greater (Enterprise Support Only). Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); upgrade to 4.2.7 or greater (Enterprise Support Only). Spring Cloud Config 4.3.x: affected from 4.3.0 through 4.3.2 (inclusive); upgrade to 4.3.3 or greater. Spring Cloud Config 5.0.x: affected from 5.0.0 through 5.0.2 (inclusive); upgrade to 5.0.3 or greater.
The base directory (`spring.cloud.config.server.git.basedir`) used by the Spring Cloud Config Server to clone Git repositories to is susceptible to time-of-check-time-of-use (TOCTOU) attacks.
Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); upgrade to 3.1.14 or greater (Enterprise Support Only). Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); upgrade to 4.1.10 or greater (Enterprise Support Only). Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); upgrade to 4.2.7 or greater (Enterprise Support Only). Spring Cloud Config 4.3.x: affected from 4.3.0 through 4.3.2 (inclusive); upgrade to 4.3.3 or greater. Spring Cloud Config 5.0.x: affected from 5.0.0 through 5.0.2 (inclusive); upgrade to 5.0.3 or greater.
CVE-2026-41004 is a vulnerability in Spring Cloud Config Server where enabling trace logging causes sensitive information to be logged in plain text. This affects multiple versions across 3.1.x, 4.1.x, 4.2.x, 4.3.x, and 5.