LiveActive security incident?Get immediate response
CVE Record

CVE-2018-12546: In Eclipse Mosquitto version 1.0 to 1.5.5 (inclusive) when a client publishes a retained message to a topic...

In Eclipse Mosquitto version 1.0 to 1.5.5 (inclusive) when a client publishes a retained message to a topic, then has its access to that topic revoked, the retained message will still be published to clients that subscribe to that topic in the future. In some applications this may result in clients being able cause effects that would otherwise not be allowed.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

Older Eclipse Mosquitto brokers may keep delivering a retained MQTT message even after the publisher loses access to that topic. In some systems, that stale retained message could trigger actions clients should no longer be able to cause. The source bundle does not provide CVSS, a patch version, or exploitation evidence.

Executive priority

Treat this as targeted hygiene for MQTT environments rather than an emergency based on the provided evidence. Prioritize review if Mosquitto controls devices, automation, or safety-relevant workflows and if retained messages are used with changing permissions.

Technical view

CVE-2018-12546 affects Eclipse Mosquitto 1.0 through 1.5.5 inclusive. The issue is access-control related: retained messages remain available to future subscribers after the original client’s topic access is revoked. The mapped weakness is CWE-284. No CVSS vector or detailed remediation is included in the provided sources.

Likely exposure

Exposure is most likely where Eclipse Mosquitto 1.0-1.5.5 is deployed, retained MQTT messages are used, and topic permissions can change after publication. Systems using retained messages to drive device or workflow behavior have higher business relevance.

Exploitation context

The provided sources do not report active exploitation, and this CVE is not marked KEV. Abuse would depend on prior ability to publish a retained message and later permission revocation. The sources do not provide exploit details or observed attacks.

Researcher notes

Evidence is limited to the CVE description and Eclipse bug reference. The key condition is retained message persistence after authorization changes. Validate behavior without publishing operationally harmful content. Do not assume all Mosquitto deployments are exposed; retained-message and ACL-change patterns matter.

Mitigation direction

  • Inventory Mosquitto brokers and flag versions 1.0 through 1.5.5.
  • Check Eclipse Mosquitto guidance for fixed versions or supported remediation.
  • Review retained-message use where topic ACLs are changed after publication.
  • Clear retained messages tied to revoked access using vendor-supported procedures.
  • Assess business workflows where retained messages can trigger operational effects.

Validation and detection

  • Confirm broker versions across production, staging, and embedded deployments.
  • Identify topics using retained messages and changing access controls.
  • Review ACL revocation workflows for retained-message cleanup expectations.
  • Test in a controlled environment whether revoked publishers’ retained messages remain deliverable.
  • Document affected topics, clients, and operational consequences before remediation.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookup
cve · low confidence lookup

CVE-2018-12546 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
The Eclipse FoundationEclipse Mosquitto1.0, unspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.