Security readout for executives and security teams
Plain-English summary
Eclipse Arrowhead’s MQTT certificate authentication can trust identity claims inside an unverified, client-supplied certificate. An unauthenticated attacker able to publish to the broker could impersonate a system operator and gain full MQTT management access. The HTTP certificate path is reportedly unaffected.
Executive priority
Treat as an immediate priority where the vulnerable MQTT configuration is enabled. The flaw can provide unauthenticated system-operator authority and broad management control. Promptly identify exposed deployments, restrict broker access, disable unnecessary MQTT functionality, and obtain Eclipse’s remediation guidance. Other deployments should still verify configuration and version status.
Technical view
When the MQTT API uses certificate authentication, CertificateMqttFilter parses an X.509 certificate from the MQTT payload but does not verify its signature or trust chain. Authorization then relies on attacker-controlled Subject DN strings. A forged identity can set isSysOp=true and pass ManagementServiceMqttFilter, affecting confidentiality and integrity across managed systems.
Likely exposure
Potentially exposed deployments run Eclipse Arrowhead 5.0.0 through 5.2.1, enable the MQTT API, use its certificate authentication policy, and permit attacker-controlled broker publishing. The narrative names this range, although the structured affected entry lists only 5.0.0; confirm exact versions with Eclipse guidance.
Exploitation context
The prerequisite is access to publish messages to the MQTT broker. Exploitation requires no Arrowhead privileges or user interaction but depends on the vulnerable MQTT configuration. The supplied record is not marked as CISA KEV, and the sources provide no evidence of active exploitation.
Researcher notes
The core weakness combines improper authentication and certificate validation failures, mapped to CWE-290 and CWE-295. Exploitability follows from trusting Subject DN fields without signature or chain validation. CVSS 4.0 is 9.5. No patch is identified in the supplied material, and the discrepancy in affected-version metadata warrants vendor confirmation.
Mitigation direction
- Check Eclipse’s advisory for an official fixed version or vendor-approved mitigation.
- Disable the MQTT API where it is not operationally required.
- Avoid the vulnerable MQTT certificate authentication policy pending vendor guidance.
- Restrict MQTT publishing to explicitly authorized, trusted clients and network paths.
- Monitor MQTT management activity for unauthorized or unexpected administrative changes.
Validation and detection
- Inventory Eclipse Arrowhead versions and reconcile them against the reported 5.0.0–5.2.1 range.
- Confirm whether the MQTT API and certificate authentication policy are enabled.
- Review broker access controls to identify who can publish to Arrowhead MQTT topics.
- Verify HTTP authentication is assessed separately; the supplied description says it is unaffected.
- Review MQTT management logs for unexpected system-operator identities or administrative actions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-290: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-82180 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.5 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——eclipseVulnerability scoring details
Base CVSS 4.0 score
9.5CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/812CVE reference, eclipse
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authentication Bypass by Spoofing
Authentication Bypass by Spoofing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.