cve.bz

CVE-2026-112185 eclipse foundation eclipse kura: Insufficiently Protected Credentials

8.6 highEPSS 0.3%

High (8.6) in eclipse foundation eclipse kura. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

8.6 high
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
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-522 Insufficiently Protected Credentials
CWE-668 Exposure of Resource to Wrong Sphere
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
Assigned by
eclipse (CNA)
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-112185 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-112185?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-112185?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-112185 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-112185

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-112185](https://cve.bz/cve/badge/CVE-2026-112185.svg)](https://cve.bz/cve/CVE-2026-112185)

HTML:

<a href="https://cve.bz/cve/CVE-2026-112185"><img src="https://cve.bz/cve/badge/CVE-2026-112185.svg" alt="CVE-2026-112185"></a>

Affected

  • eclipse foundation:eclipse kura

Versions

From the CNA's record in the CVE List.

ProductAffected
Eclipse Foundation Eclipse Kurafrom 5.1.0 through 5.6.2

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-522 (13).

History

  1. The NVD deferred its analysis

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON