CVE-2026-82180
CRITICALDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 13% of all known CVEs.
References
Related Vulnerabilities
Other CWE-290 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-4358 | Critical | 9.8 | 97% | KEV | - |
| CVE-2022-24112 | Critical | 9.8 | 96% | KEV | Fix |
| CVE-2022-23131 | Critical | 9.1 | 96% | KEV | - |
| CVE-2021-29441 | High | 8.6 | 88% | - | Fix |
| CVE-2019-1234 | High | 7.5 | 75% | - | - |
| CVE-2021-31195 | Medium | 6.5 | 74% | - | Fix |
Common questions
How do I fix CVE-2026-82180?
No published fix for CVE-2026-82180 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-82180 being actively exploited?
Not that we know of. CVE-2026-82180 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.22% is the estimated probability that it will be exploited in the next 30 days. That is higher than 13% of all scored CVEs.
How severe is CVE-2026-82180?
CVE-2026-82180 has a CVSS v4 base score of 9.5, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-82180
Markdown
[](https://tridentstack.com/cve/CVE-2026-82180)HTML
<a href="https://tridentstack.com/cve/CVE-2026-82180"><img src="https://tridentstack.com/cve/badge/CVE-2026-82180.svg" alt="CVE-2026-82180"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-03.