In Eclipse Kura versions 5.4.0 through 5.6.2, the Identity REST APIs (identity/v1, and identity/v2 since 5.5.0, provided by…
Affects Eclipse Kura 5.4.0 through 5.6.2 for identities holding the rest.identity permission but not kura.admin. The issue is fixed in Kura 5.6.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- 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. Affects Eclipse Kura 5.4.0 through 5.6.2; identity/v2 applies since 5.5.0. Requires an authenticated identity holding the rest.identity permission but not kura.admin.
- 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 Identity REST APIs (identity/v1 and identity/v2) fail to check permission changes against the requester's own rights, and an attacker can reach them remotely after logging in with a high-privilege account. An attacker holding only the rest.identity permission can grant itself full administrative rights, change or delete more privileged accounts including administrators, and lock legitimate administrators out of the device.
Read the original description
In Eclipse Kura versions 5.4.0 through 5.6.2, the Identity REST APIs (identity/v1, and identity/v2 since 5.5.0, provided by org.eclipse.kura.rest.identity.provider) do not check identity and permission management requests against the permissions of the requesting identity. An authenticated identity holding the rest.identity permission, but not kura.admin, can assign any permission to any identity, including kura.admin to itself. It can also change the password of, or delete, identities holding more privileges than its own, including administrators, and create or delete permissions. This allows escalation to full administrative privileges and can lock legitimate administrators out of the device. 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.
Affects Eclipse Kura 5.4.0 through 5.6.2; identity/v2 applies since 5.5.0. Requires an authenticated identity holding the rest.identity permission but not kura.admin.Upgrade 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-112191 (In Eclipse Kura versions 5.4.0 through 5.6.2, the Identity REST APIs (identity/v1, and identity/v2 since 5.5.0, provided by…), 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-112191 (entry last updated 2026-11-10): Affected: - Eclipse Foundation Eclipse Kura: from 5.4.0, through 5.6.2 Fixed versions: 5.6.3. Conditions (all must be true for the bug to be hit): - Affects Eclipse Kura 5.4.0 through 5.6.2; identity/v2 applies since 5.5.0. (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/431) - Requires an authenticated identity holding the rest.identity permission but not kura.admin. (source: https://gitlab.eclipse.org/security/cve-assignment/-/work_items/431) 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-112191 is not listed as of cve.now's last read. This KEV status is for CVE-2026-112191 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-v8gf-9w4p-662w - https://gitlab.eclipse.org/security/cve-assignment/-/work_items/431 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-112191 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-112191.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Eclipse Foundation Eclipse Kura
From 5.4.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-112191
Is CVE-2026-112191 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 Identity REST APIs let an authenticated identity with the rest.identity permission, but not kura.admin, assign any permission to any identity, including kura.admin to itself. It can also change passwords of or delete more privileged identities, including administrators, which allows escalation to full administrative privileges and can lock legitimate administrators out of the device.Source: gitlab.eclipse.org
Which versions are affected by CVE-2026-112191?
Eclipse Kura: from 5.4.0 through 5.6.2.Source: cve.now feed data
Am I affected, and how do I check?
Eclipse Kura versions 5.4.0 through 5.6.2 are affected, and the identity/v2 API applies since 5.5.0. To check, look at the Kura version installed on the device and whether the identity with the rest.identity permission is not also granted kura.admin.Source: gitlab.eclipse.org
How do I fix CVE-2026-112191?
Upgrade Eclipse Kura to 5.6.3, which contains the fix.Source: gitlab.eclipse.org