GHSA-w3x5-427h-wfq6
HIGHSpring Boot Admins integrated notifier support allows arbitrary code execution
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
de.codecentric:spring-boot-admin☕de.codecentric:spring-boot-admin☕de.codecentric:spring-boot-adminReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
All users who run Spring Boot Admin Server, having enabled Notifiers (e.g. Teams-Notifier) and write access to environment variables via UI are possibly affected.
Patches
In the most recent releases of Spring Boot Admin 2.6.10 and 2.7.8 the issue is fixed by implementing SimpleExecutionContext of SpEL. This prevents the arbitrary code execution (i.e. SpEL injection).
Workarounds
- Disable any notifier
- Disable write access (POST request) on
/envactuator endpoint
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | de.codecentric:spring-boot-admin | all versions | 2.6.10 |
| ☕Maven | de.codecentric:spring-boot-admin | ≥ 2.7.0&&< 2.7.8 | 2.7.8 |
| ☕Maven | de.codecentric:spring-boot-admin | ≥ 3.0.0-M1&&< 3.0.0-M6 | 3.0.0-M6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for de.codecentric:spring-boot-admin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update de.codecentric:spring-boot-admin to 2.6.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w3x5-427h-wfq6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w3x5-427h-wfq6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w3x5-427h-wfq6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w3x5-427h-wfq6 in your dependencies?
O3 detects GHSA-w3x5-427h-wfq6 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.