Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

Quick assessment

Affected
Eclipse Foundation eclipse-hawkbit/hawkbit
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Eclipse hawkBit是Eclipse基金会的一个软件更新管理平台。 Eclipse hawkBit 1.0.3及之前版本存在安全漏洞,该漏洞源于Direct Device Integration (DDI) Controller中存在对象级授权验证缺陷,允许已通过身份验证的设备权限提升,绕过更新分配边界,下载同一租户内的任意固件工件。

CVSS 4.3 · Medium EPSS 0.36% · P27

Affected Version Matrix 2

VendorProduct Version RangeStatus
Eclipse Foundation eclipse-hawkbit/hawkbit ≤ 1.0.3 affected
1.0.4 unaffected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-16454

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Privilege Escalation in Eclipse hawkBit DDI allows Tenant-Isolated Firmware Exfiltration
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
访问控制不恰当
Source: CVE Program / CVE List V5
Vulnerability Title
Eclipse hawkBit 权限许可和访问控制问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Eclipse hawkBit是Eclipse基金会的一个软件更新管理平台。 Eclipse hawkBit 1.0.3及之前版本存在安全漏洞,该漏洞源于Direct Device Integration (DDI) Controller中存在对象级授权验证缺陷,允许已通过身份验证的设备权限提升,绕过更新分配边界,下载同一租户内的任意固件工件。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
Eclipse Foundation eclipse-hawkbit/hawkbit 0 ~ 1.0.3 -

II. Public POCs for CVE-2026-16454

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-16454

请登录查看更多情报信息。

Other References for CVE-2026-16454 (2)

Same Patch Batch · Eclipse Foundation · 2026-07-21 · 4 CVEs total

CVE-2026-16439 Eclipse OpenJ9 : Using -Xtrace to trace method arguments can lead to buffer underflow
CVE-2026-16243 Eclipse OMR : arraycmp SIMD implementation does not check if the number of bytes to compar
CVE-2026-16441 Eclipse OpenJ9 : Method resolution default method precedence failure

IV. Related Vulnerabilities

V. Comments for CVE-2026-16454

No comments yet


Leave a comment