Org.eclipse.hawkbit:hawkbit ddi resource: Eclipse hawkBit DDI has Privilege Escalation that allows Tenant-Isolated
Affects org.eclipse.hawkbit:hawkbit-ddi-resourceSource GCVE Database
Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.0.4 when convenient.
Data as of 6 Nov 2026, 23:24 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.0.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 21 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade org.eclipse.hawkbit:hawkbit-ddi-resource to 1.0.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Mavenorg.eclipse.hawkbit:hawkbit-ddi-resource | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade affected installations to Eclipse hawkBit version 1.0.4 or later. This version includes fixes that enforce assignment-based authorization checks on every firmware artifact download request and restrict access to software module metadata endpoints to only assigned or installed artifacts. No additional mitigations are required beyond applying the official patch.
Description
A privilege escalation vulnerability exists in Eclipse hawkBit Direct Device Integration (DDI) Controller versions 1.0.3 and earlier. Authenticated devices within a tenant can bypass assignment restrictions and download any firmware artifact assigned to that tenant, rather than only those explicitly assigned to them. This flaw is due to improper object-level authorization validation. The vulnerability has moderate severity with low confidentiality impact, as access is limited to the tenant scope and firmware binaries typically do not contain sensitive data. The issue is fixed in version 1.0.4.
References
- github.com/eclipse-hawkbit/hawkbit/security/advisories/GHSA-92r3-p8c2-3fpx (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-16454 (opens in a new tab)
- github.com/eclipse-hawkbit/hawkbit/pull/3156 (opens in a new tab)
- github.com/eclipse-hawkbit/hawkbit/pull/3161 (opens in a new tab)
- github.com/eclipse-hawkbit/hawkbit/commit/6cb34fd77f6a60cfb0ee5b379093593cbe56591a (opens in a new tab)
- github.com/eclipse-hawkbit/hawkbit/commit/914b8b406bd77838cffbef80c1ea4cff5a15c710 (opens in a new tab)
- github.com/eclipse-hawkbit/hawkbit (opens in a new tab)
- github.com/eclipse-hawkbit/hawkbit/releases/tag/1.0.4 (opens in a new tab)
- gitlab.eclipse.org/security/cve-assignment/-/work_items/196 (opens in a new tab)