CVE-2026-111249 · Package
NO FIX YET · SEE WHAT TO DO
The development-time LiveReload server in the embedded Maven plugin listens on all network interfaces without authentication and accepts websocket connections from any origin. A network attacker or a malicious web page visited by the developer can learn changed file names, the server version, and reach deployed applications through the extra port.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only projects that enable LiveReload in the embedded Maven plugin during development are exposed. The server listens on all interfaces, so developer machines on shared or untrusted networks are the main concern. Production deployments and builds without LiveReload enabled can skip it.
Not affected if default-config, livereload-disabled, production-only
Who cares dev-tooling, java, maven, undertow
netstat -an | grep LISTEN or similar10.3.0 or 11.0.0-M2, which the description states fix the issueThe development-time LiveReload support listens on all network interfaces without authentication and accepts websocket connections from any origin. A network attacker, or a web page visited by the developer, can observe the names of changed files in the watched folder and the server version, and reach the deployed applications through the additional port. This only affects LiveReload enabled in the embedded Maven plugin. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.