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

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-82180

Quick assessment

Affected
Eclipse Foundation Eclipse Arrowhead
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 Arrowhead 5.0.0 至 5.2.1 版本中，当启用了基于证书认证的 MQTT API 时， 会解析客户端在 MQTT 消息载荷（ 的 authentication 字段）中发送的 X.509 证书，并将其 Subject DN 视为已认证的身份。该证书通过 进行解码，但其签名从未被验证，其颁发者链也从未对照任何信任存储进行校验。 认证过程被简化为针对攻击者提供数据的两个字符串比较： 1. DN 限定符必须等于 或 ； 2. CN 中的云名称部分必须与服务器自身的云名称匹配。 这两个值

CVSS 9.5 · Critical

Affected Version Matrix 1

VendorProduct Version RangeStatus
Eclipse Foundation Eclipse Arrowhead 5.0.0≤ 5.2.1 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-82180

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
N/A
Source: CVE Program / CVE List V5
Vulnerability Description
In Eclipse Arrowhead versions from 5.0.0 to 5.2.1 when the MQTT API is enabled with the certificate authentication policy, CertificateMqttFilter parses an X.509 certificate that the client sends inside the MQTT message payload (the authentication field of MqttRequestTemplate) and treats its Subject DN as the authenticated identity. The certificate is decoded with CertificateFactory.generateCertificate() but its signature is never verified and its issuer chain is never validated against any trust store. Authorisation is reduced to two string comparisons on attacker-supplied data: the DN-qualifier must equal "sy" or "op", and the cloud-name part of the CN must match the server's. Both values are public (the cloud name is in the server's own TLS certificate). An attacker who can publish to the MQTT broker can therefore mint a self-signed certificate with CN=Sysop.<cloud>.<org>.arrowhead.eu, dnQualifier=op, send it as the authentication field, and be authenticated as the cloud's system operator with isSysOp == true. This passes the downstream ManagementServiceMqttFilter (request.isSysOp() → allowed) and gives full management access over MQTT. The HTTP CertificateFilter is not affected — it reads the certificate from jakarta.servlet.request.X509Certificate, which Tomcat populates only after a successful mTLS handshake against the configured trust store.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:H
Source: CVE Program / CVE List V5
Vulnerability Type
证书验证不恰当
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Eclipse Foundation Eclipse Arrowhead 5.0.0 ~ 5.2.1 -

II. Public POCs for CVE-2026-82180

# 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-82180

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

Vendor Advisories for CVE-2026-82180 (1)

Same Patch Batch · Eclipse Foundation · 2026-09-03 · 4 CVEs total

CVE-2026-80515 8.9 HIGH Eclipse Arrowhead 5.0.0-5.2.1 认证授权绕过
CVE-2026-85199 8.8 HIGH CVE-2026-85199
CVE-2026-84736 8.3 HIGH Eclipse aeriOS Federator默认禁用TLS证书校验漏洞

IV. Related Vulnerabilities

Same product: Eclipse Arrowhead
Same vendor: Eclipse Foundation
Same weakness: CWE-295

V. Comments for CVE-2026-82180

No comments yet

Leave a comment