CVE-2026-82180
MQTT auth flaw allows forged X.509 in payload to obtain sysop management access.
Is CVE-2026-82180 being exploited?
Not confirmed. CVE-2026-82180 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-82180?
CVE-2026-82180 is rated Critical. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82180?
Yes. A fix has been recorded for CVE-2026-82180. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82180 affect?
CVE-2026-82180 affects Eclipse Arrowhead 5.0.0 - 5.2.1 (MQTT API with certificate authentication enabled). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82180?
Upgrade Arrowhead or disable MQTT certificate auth; restrict who can publish to the MQTT broker.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Auth bypass: attacker can supply a self-signed cert in MQTT payload to become isSysOp and gain full management access over MQTT.
Immediate action required
- affected>= 5.0.0 and <= 5.2.1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.