# CVE-2026-16454: Privilege Escalation in Eclipse hawkBit DDI allows Tenant-Isolated Firmware Exfiltration

> Authenticated devices can bypass authorization checks to download or list any firmware artifact within their tenant, leading to data exfiltration.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-92r3-p8c2-3fpx, GHSA-f3j8-8ggq-f9x2

## What is CVE-2026-16454?

CVE-2026-16454 is a medium-severity missing authorization vulnerability in eclipse-hawkbit/hawkbit, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Eclipse hawkBit versions 1.0.3 and prior, a privilege escalation vulnerability (CWE-284 / CWE-862) has been identified in the Direct Device Integration (DDI) Controller.

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.

Weakness: CWE-862 (Missing Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-16454?

It affects 1 product.


Products: Eclipse Hawkbit.

## How do I fix CVE-2026-16454?

No fix has been published for CVE-2026-16454 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-16454 being exploited?

There is no known exploitation of CVE-2026-16454 in the wild and no public exploit code.

## Other vulnerabilities in eclipse-hawkbit/hawkbit

- [CVE-2019-10240](https://insights.sbomify.com/CVE-2019-10240/): Cleartext Transmission of Sensitive Information, Inclusion of Functionality from Untrusted Control Sphere , and Download of Code Without Integrity Check in Eclipse hawkBit (high 8.1)
- [CVE-2020-27219](https://insights.sbomify.com/CVE-2020-27219/): Cross-site Scripting in Eclipse Hawkbit (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-16454 and fix it if it is affected.

What it is: CVE-2026-16454 is a medium-severity missing authorization vulnerability in eclipse-hawkbit/hawkbit, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16454 in the wild and no public exploit code.

Affected product: eclipse-hawkbit/hawkbit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-16454/ (Markdown: https://insights.sbomify.com/CVE-2026-16454/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-16454
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-16454
- OSV: https://osv.dev/vulnerability/CVE-2026-16454

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-16454/
Summaries are generated and may contain mistakes; the official description above is the record.