Micronaut management endpoints vulnerable to drive-by localhost attackGHSA-583g-g682-crxf
MEDIUMFix: micronaut-projects/micronaut-core#8642GHSA-583g-g682-crxf is a medium-severity (CVSS 5.1) CWE-15 vulnerability in io.micronaut:micronaut-http-server. A fix is available for io.micronaut:micronaut-http-server — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-583g-g682-crxf.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
io.micronaut:micronaut-http-server☕io.micronaut:micronaut-http-server-netty☕io.micronaut:micronaut-http-server-tckReal-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
Micronaut Framework is a modern, JVM-based, full stack Java framework designed for building modular, easily testable JVM applications with support for Java, Kotlin and the Groovy language. Enabled but unsecured management endpoints are susceptible to drive-by localhost attacks. While not typical of a production application, these attacks may have more impact on a development environment where such endpoints may be flipped on without much thought. A malicious/compromised website can make HTTP requests to localhost. Normally, such requests would trigger a CORS preflight check which would prevent the request; however, some requests are "simple" and do not require a preflight check. These endpoints, if enabled and not secured, are vulnerable to being triggered. Production environments typically disable unused endpoints and secure/restrict access to needed endpoints. A more likely victim is the developer in their local development host, who has enabled endpoints without security for the sake of easing development. This issue has been addressed in version 3.8.3. Users are advised to upgrade.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | io.micronaut:micronaut-http-server | all versions | 3.8.3io.micronaut:micronaut-http-server:3.8.3 |
| ☕Maven | io.micronaut:micronaut-http-server-netty | all versions | 3.8.3io.micronaut:micronaut-http-server-netty:3.8.3 |
| ☕Maven | io.micronaut:micronaut-http-server-tck | all versions | 3.8.3io.micronaut:micronaut-http-server-tck:3.8.3 |
Affected Products
micronautobjectcomputingDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.micronaut:micronaut-http-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update io.micronaut:micronaut-http-server to 3.8.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-583g-g682-crxf 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.
Frequently Asked Questions
Is GHSA-583g-g682-crxf in your dependencies?
Find it across Maven, including transitive dependencies.