Read the docs

Eclipse Kura Identity REST APIs let users escalate privileges

Priority HIGH 72CWE-269Published · Updated

Key facts

Attack vector
Network
Privileges required
High
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Privilege escalation, Security bypass
Confidentiality · integrity · availability
High · High · High
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-269 and CWE-863.

Summary

Eclipse Kura versions 5.4.0 through 5.6.2 provide Identity REST APIs that do not check identity and permission management requests against the requesting identity's permissions (CWE-863). An authenticated identity with rest.identity but not kura.admin can grant itself kura.admin. It can also change passwords of or delete more privileged identities, which allows full administrative access and can lock administrators out.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00294 22nd percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
Eclipse FoundationEclipse Kura5.4.0 – 5.6.2—No fix listedCNA
  • Eclipse Kura VendorEclipse Foundation Affected 5.4.0 – 5.6.2 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:eclipse:kura:*:*:*:*:*:*:*:*——Eclipse Foundation

Remediation

Update Eclipse Kura to version 5.6.3, which fixes this issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-16

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-112191
  2. 2026-11-10 Alias added: GHSA-xc4c-5vw7-m8p2
  3. 2026-11-12 Priority changed: MEDIUM → LOW
  4. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2023-23979 HTTP/2 request cancellation lets attackers exhaust server resources KEVCVSS 3.1HIGH 7.5
  • TI-2026-81947 Unauthenticated command injection in Eclipse Che che-machine-exec CVSS 3.1CRITICAL 9.8
  • TI-2026-13216 CWE-863: ABAC authorization bypass via trailing slash route normalization in Eclipse BaSyx Go Components CVSS 3.1CRITICAL 9.8
  • TI-2026-06514 Path traversal in Eclipse BaSyx CVSS 3.1CRITICAL 10.0
  • TI-2026-01382 In the Eclipse Theia Website repository, the GitHub Actions workflow… CVSS 3.1CRITICAL 10.0
  • TI-2026-74697 Authentication bypass in Eclipse Jetty EthereumAuthenticator CVSS 4.0CRITICAL 9.3
See all 482 →

Sources