Loading vulnerability…
CVE-2025-22235 is a vulnerability in Spring Boot affecting use of EndpointRequest.to() in Spring Security configurations. When EndpointRequest.to() is created for an actuator endpoint that is disabled or not exposed over the web, it can generate a matcher for null/** rather than the intended actuator endpoint. This can cause security rules to be bound to an unintended path pattern instead of the expected management endpoint. In affected applications, requests to application paths such as /null may therefore be matched and handled differently than intended, creating a security policy enforcement flaw.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (POC) for CVE-2025-22235, a vulnerability in Spring Boot/Spring Security where improper use of EndpointRequest.to() in security configuration can result in authentication bypass. The repository contains a demo Spring Boot application (Java) with a vulnerable SecurityConfig that uses EndpointRequest.to("health") for an endpoint that is not actually exposed, causing Spring Boot to generate a matcher for /null/**. As a result, the /null endpoint can be accessed without authentication, demonstrating the flaw. The repository includes scripts to start the demo application (start_demo.sh, start_demo.bat), a Python script (test_vulnerability.py) to automate vulnerability testing, and all necessary configuration and code files. The main exploit capability is unauthenticated access to a sensitive endpoint due to a misconfigured security matcher. The repository targets several versions of Spring Security and Spring Boot as listed in the README. The endpoints of interest are /null (vulnerable), /info (protected), and the actuator endpoints for health and info. The code is structured as a standard Maven-based Java project with clear separation of application, controller, security configuration, and test scripts.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.