In Eclipse Kura versions 5.1.0 through 5.6.2, the Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) does not…
- Exploited
- No known exploitation
- Fix
- Fixed in 5.6.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Eclipse Kura versions 5.1.0 through 5.6.2 Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) with UserAdmin configuration exposed Attacker must be an authenticated identity holding the rest.configuration permission
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original 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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Eclipse Kura versions 5.1.0 through 5.6.2 Configuration REST API v2 (org.eclipse.kura.rest.configuration.provider) with UserAdmin configuration exposed Attacker must be an authenticated identity holding the rest.configuration permissionUpgrade to a fixed version: 5.6.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
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.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Eclipse Foundation Eclipse Kura
From 5.1.0 · through 5.6.2
Evidence 4
Vendor advisory · 2
Establishes: Affected and fixed versions.
- Advisory
- Link
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-112185
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: cve.now feed data
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: gitlab.eclipse.org
Which versions are affected by CVE-2026-112185?
Eclipse Kura: from 5.1.0 through 5.6.2.Source: cve.now feed data
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: gitlab.eclipse.org
How do I fix CVE-2026-112185?
Upgrade Eclipse Kura to version 5.6.3, which fixes the issue.Source: gitlab.eclipse.org