Answer in brief
CVE-2026-16454 records a Medium severity (CVSS 4.3) vulnerability in Eclipse hawkBit DDI has Privilege Escalation that allows Tenant-Isolated Firmware Exfiltration. The current sources do not mark it as known exploited. The current feed maps org.eclipse.hawkbit:hawkbit-ddi-resource (maven). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps org.eclipse.hawkbit:hawkbit-ddi-resource (maven). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:eclipse:hawkbit:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| org.eclipse.hawkbit:hawkbit-ddi-resourcemaven | <=1.0.3 | 1.0.4 |
Published upstream
Jul 21, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Aug 12, 2026
## **Description** A privilege escalation vulnerability has been identified in the Direct Device Integration (DDI) Controller of **Eclipse hawkBit** (versions 1.0.3 and prior). This vulnerability allows an authenticated device to escalate its permissions and bypass the strict boundaries of its assigned updates. Under normal operation, a device should be restricted **strictly to the specific firmware artifacts explicitly assigned to it**. However, this flaw enables any authenticated device to bypass this restriction and download any firmware artifact **within the same tenant**. This is **not** an authentication bypass; the requesting device must possess valid credentials for its respective tenant. Instead, the issue stems from a flaw in object-level authorization validation. A related, lower-severity helper issue exists in the listing software modules artifacts metadata endpoint. This endpoint does not enforce assignment checks, enabling an authenticated device to list and enumerate available firmware artifacts, which can facilitate targeted exfiltration using the main download authorization bypass. --- ## **Impact** * **Severity:** Moderate * **Scope:** Tenant-isolated. An attacker must be an authenticated device within the target tenant to exploit this vulnerability. * **Confidentiality Impact:** **Low**. While firmware binaries can be retrieved, the impact is mitigated because access is restricted strictly to the scope of the pre-authenticated tenant, and no administrative or cross-tenant data is exposed. Additionally, production firmware binaries are by design not expected to contain highly sensitive or confidential data (such as hardcoded credentials or private keys), further supporting the Low confidentiality rating. --- ## **Affected Products and Versions** * **Product:** `eclipse-hawkbit/hawkbit` * **Affected Component:** `hawkbit-ddi/hawkbit-ddi-resource`, as well as the compiled binaries and Docker images that contain this component. * **Affected Versions:** `1.0.3` and prior versions. * **Patched Version:** `1.0.4` --- ## **Remediation** Upgrade to version **1.0.4** or later. **Fix details:** The download authorization logic has been corrected to ensure that assignment-based verification is executed on every artifact download request. Additionally, the software module metadata endpoint has been updated to enforce proper authorization, restricting access exclusively to software modules and artifacts that are explicitly assigned to or already installed on the requesting device. --- ## **Credits** Eclipse would like to thank **Santosh Kumar Puppala** (GitHub: [Santoshkumarpuppala](https://github.com/Santoshkumarpuppala), Email: [email protected]) for discovering and reporting this vulnerability through coordinated disclosure.
Quoted source text, attributed separately from HOL analysis.