CVE-2026-54412

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-06-14. a secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

LiamBindle MQTT-C through version 1.1.6 contains a heap-based out-of-bounds read and integer underflow in the mqtt_unpack_publish_response() function in src/mqtt.c that allows a remote unauthenticated attacker controlling an MQTT broker - or able to inject MQTT traffic into an unencrypted session - to crash a subscribed MQTT-C client and potentially disclose adjacent heap memory by sending a single crafted PUBLISH packet. The function validates only that the fixed-header remaining_length is at least 4, then reads the 16-bit topic_name_size field from the broker-controlled packet and advances the parse pointer by that value without verifying that topic_name_size plus the surrounding overhead fits within remaining_length; it subsequently computes application_message_size as remaining_length - topic_name_size - 2 (QoS 0) or - 4 (QoS greater than 0) in unsigned arithmetic, producing an integer underflow that is then passed to memmove(). A PUBLISH packet with topic_name_size = 0xFFFF and remaining_length = 7 advances the parse pointer 65535 bytes past the receive buffer (out-of-bounds read) and causes an application_message_size near 2^32, crashing the process when the resulting memmove() is executed.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
33.3%
KEV
Not listed

Published

June 14, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jun 15, 2026
⚠️ Active exploitation confirmed. No patch confirmed yet.
generic

CWE - CWE-191: Integer Underflow (Wrap or Wraparound) (4.20)

https://cwe.mitre.org/data/definitions/191.html
generic🔴 Active Exploitation

CWE - CWE-125: Out-of-bounds Read (4.20)

https://cwe.mitre.org/data/definitions/125.html
generic

MQTT-C/src/mqtt.c at v1.1.6 · LiamBindle/MQTT-C · GitHub

https://github.com/LiamBindle/MQTT-C/blob/v1.1.6/src/mqtt.c#L1334
generic

GitHub - LiamBindle/MQTT-C: A portable MQTT C client for embedded systems and PCs alike. · GitHub

https://github.com/LiamBindle/MQTT-C

Vendor Advisories for CVE-2026-54412(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 86× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 119 total refreshes for this CVE.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:19 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 23:09 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-16 05:05 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 15:59 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-15 01:28 UTCGHSA enrichment
  19. 2026-07-14 11:54 UTCGHSA enrichment
  20. 2026-07-13 22:43 UTCGHSA enrichment
  21. 2026-07-13 22:31 UTCEPSS rescore
  22. 2026-07-13 09:36 UTCGHSA enrichment
  23. 2026-07-13 06:13 UTCEPSS rescore
  24. 2026-07-13 06:13 UTCEPSS rescore
  25. 2026-07-12 19:18 UTCGHSA enrichment
Show 75 more
  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-12 05:01 UTCGHSA enrichment
  3. 2026-07-11 15:54 UTCGHSA enrichment
  4. 2026-07-11 08:27 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 02:48 UTCGHSA enrichment
  7. 2026-07-10 12:50 UTCGHSA enrichment
  8. 2026-07-09 21:32 UTCGHSA enrichment
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-09 05:12 UTCGHSA enrichment
  12. 2026-07-08 16:07 UTCGHSA enrichment
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-08 03:00 UTCGHSA enrichment
  16. 2026-07-07 13:50 UTCGHSA enrichment
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 13:46 UTCEPSS rescore
  19. 2026-07-07 00:43 UTCGHSA enrichment
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-06 01:41 UTCGHSA enrichment
  25. 2026-07-05 12:35 UTCGHSA enrichment
  26. 2026-07-05 02:31 UTCEPSS rescore
  27. 2026-07-05 02:30 UTCEPSS rescore
  28. 2026-07-04 23:26 UTCGHSA enrichment
  29. 2026-07-04 10:18 UTCGHSA enrichment
  30. 2026-07-04 06:31 UTCEPSS rescore
  31. 2026-07-04 06:31 UTCEPSS rescore
  32. 2026-07-03 14:58 UTCGHSA enrichment
  33. 2026-07-03 01:51 UTCGHSA enrichment
  34. 2026-07-02 12:46 UTCGHSA enrichment
  35. 2026-07-01 23:40 UTCGHSA enrichment
  36. 2026-07-01 15:07 UTCEPSS rescore
  37. 2026-07-01 10:35 UTCGHSA enrichment
  38. 2026-06-30 23:22 UTCEPSS rescore
  39. 2026-06-30 21:25 UTCGHSA enrichment
  40. 2026-06-30 08:19 UTCGHSA enrichment
  41. 2026-06-29 19:14 UTCGHSA enrichment
  42. 2026-06-29 14:06 UTCEPSS rescore
  43. 2026-06-29 14:06 UTCEPSS rescore
  44. 2026-06-29 06:09 UTCGHSA enrichment
  45. 2026-06-28 16:22 UTCGHSA enrichment
  46. 2026-06-28 14:07 UTCEPSS rescore
  47. 2026-06-28 04:56 UTCEPSS rescore
  48. 2026-06-28 04:56 UTCEPSS rescore
  49. 2026-06-28 03:17 UTCGHSA enrichment
  50. 2026-06-27 14:12 UTCGHSA enrichment
  51. 2026-06-27 03:08 UTCEPSS rescore
  52. 2026-06-27 01:06 UTCGHSA enrichment
  53. 2026-06-26 12:01 UTCGHSA enrichment
  54. 2026-06-25 22:48 UTCGHSA enrichment
  55. 2026-06-25 13:49 UTCEPSS rescore
  56. 2026-06-25 09:42 UTCGHSA enrichment
  57. 2026-06-24 20:37 UTCGHSA enrichment
  58. 2026-06-24 14:05 UTCEPSS rescore
  59. 2026-06-24 04:20 UTCGHSA enrichment
  60. 2026-06-23 21:33 UTCEPSS rescore
  61. 2026-06-23 21:33 UTCEPSS rescore
  62. 2026-06-23 15:08 UTCGHSA enrichment
  63. 2026-06-23 01:54 UTCGHSA enrichment
  64. 2026-06-22 14:25 UTCEPSS rescore
  65. 2026-06-22 14:25 UTCEPSS rescore
  66. 2026-06-22 12:48 UTCGHSA enrichment
  67. 2026-06-21 23:42 UTCGHSA enrichment
  68. 2026-06-21 14:56 UTCEPSS rescore
  69. 2026-06-21 14:56 UTCEPSS rescore
  70. 2026-06-21 09:50 UTCGHSA enrichment
  71. 2026-06-21 01:59 UTCEPSS rescore
  72. 2026-06-21 01:59 UTCEPSS rescore
  73. 2026-06-20 20:18 UTCGHSA enrichment
  74. 2026-06-20 06:44 UTCGHSA enrichment
  75. 2026-06-19 19:26 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-54412?
CVE-2026-54412 is a high vulnerability published on June 14, 2026. LiamBindle MQTT-C through version 1.1.6 contains a heap-based out-of-bounds read and integer underflow in the mqttunpackpublishresponse() function in src/mqtt.c that allows a remote unauthenticated attacker controlling an MQTT broker - or able to inject MQTT traffic into an unencrypted session - to…
When was CVE-2026-54412 disclosed?
CVE-2026-54412 was first published in the National Vulnerability Database on June 14, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54412 actively exploited?
CVE-2026-54412 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54412?
CVE-2026-54412 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-54412?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54412, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54412

Explore →

Is Your Infrastructure Affected by CVE-2026-54412?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.