ORG.ECLIPSE.HAWKBIT:HAWKBIT-DDI-RESOURCE · CVE-2026-16454 · Package
FIX → 1.0.4
Eclipse hawkBit's DDI controller does not check artifact assignment on firmware downloads, so any authenticated device can fetch any firmware artifact within its own tenant. The metadata endpoint that lists software module artifacts also lacks assignment checks, which helps an attacker enumerate targets.
first public Jun 26, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Deployments running the hawkBit DDI controller at version 1.0.3 or earlier are exposed, since devices authenticate to it to receive updates. The attacker must already hold valid device credentials for the same tenant, so deployments with no device fleet or with single-tenant access controls are lower risk. Teams that only use the management API and not DDI can skip it, though the sources do not say this explicitly.
Not affected if hawkbit-1.0.4-or-later, no-ddi-endpoint
Who cares cwe-284, cwe-862, firmware-updates, hawkbit, iot, java
org.eclipse.hawkbit:hawkbit-ddi-resource in your build files or running images, and flag anything at or below 1.0.3.Upgrade to 1.0.4
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.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
org.eclipse.hawkbit:hawkbit-ddi-resource upgrade to 1.0.4 or later.eclipse-hawkbit/hawkbithawkbit-ddi/hawkbit-ddi-resource, as well as the compiled binaries and Docker images that contain this component.1.0.3 and prior versions.1.0.4Upgrade 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.
Eclipse would like to thank Santosh Kumar Puppala (GitHub: Santoshkumarpuppala, Email: santhoshkumar7794@gmail.com) for discovering and reporting this vulnerability through coordinated disclosure.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.