CVE-2025-66168

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 47% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

WARNING:

Users of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases.

See the  following for more details: https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt https://www.cve.org/CVERecord?id=CVE-2026-40046

Original Report:

Apache ActiveMQ does not properly validate the remaining length field which may lead to an overflow during the decoding of malformed packets. When this integer overflow occurs, ActiveMQ may incorrectly compute the total Remaining Length and subsequently misinterpret the payload as multiple MQTT control packets which makes the broker susceptible to unexpected behavior when interacting with non-compliant clients. This behavior violates the MQTT v3.1.1 specification, which restricts Remaining Length to a maximum of 4 bytes. The scenario occurs on established connections after the authentication process. Brokers that are not enabling mqtt transport connectors are not impacted.

This issue affects Apache ActiveMQ: before 5.19.2, 6.0.0 to 6.1.8, and 6.2.0

Users are recommended to upgrade to version 5.19.2, 6.1.9, or 6.2.1, which fixes the issue.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

Published

March 4, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
Patch available.
generic

oss-security - CVE-2025-66168: Apache ActiveMQ, Apache ActiveMQ All Module, Apache ActiveMQ MQTT Module: MQTT control packet remaining length field is not properly validated

http://www.openwall.com/lists/oss-security/2026/03/03/5
generic
https://www.cve.org/CVERecord?id=CVE-2026-40046
generic
https://lists.apache.org/thread/13n8mkrb2jf2y6yyhpgrkmpqcm7djyto
generic
https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt

Affected Packages

(6 across 4 ecosystems)
Maven(3)
PackageVulnerable rangeFix by version rangeDependents
org.apache.activemq:activemq-all6.2.0
  • every version up to 5.19.2: fixed in 5.19.2
  • 6.0.0 up to 6.1.9: fixed in 6.1.9
  • 6.2.0 up to 6.2.1: fixed in 6.2.1
—
org.apache.activemq:activemq-mqtt6.2.0
  • every version up to 5.19.2: fixed in 5.19.2
  • 6.0.0 up to 6.1.9: fixed in 6.1.9
  • 6.2.0 up to 6.2.1: fixed in 6.2.1
—
org.apache.activemq:apache-activemq6.2.0
  • every version up to 5.19.2: fixed in 5.19.2
  • 6.0.0 up to 6.1.9: fixed in 6.1.9
  • 6.2.0 up to 6.2.1: fixed in 6.2.1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
activemq5.16.1-1 ... 5.17.6+dfsg-2 (8 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
activemq5.17.2+dfsg-2, 5.17.2+dfsg-2+deb12u1, 5.17.6+dfsg-1, 5.17.6+dfsg-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
activemq5.17.6+dfsg-2
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 27× 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 204 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2025-66168?
CVE-2025-66168 is a high vulnerability published on March 4, 2026. WARNING: Users of 6.x should upgrade to 6.2.4 or later as the fix was missed in previous 6.x releases. See the following for more details: https://activemq.apache.org/security-advisories.data/CVE-2026-40046-announcement.txt https://www.cve.org/CVERecord?id=CVE-2026-40046 Original Report: Apache…
When was CVE-2025-66168 disclosed?
CVE-2025-66168 was first published on March 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-66168 actively exploited?
CVE-2025-66168 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-66168?
CVE-2025-66168 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-66168?
A fix for CVE-2025-66168 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-66168

Explore →

Is Your Infrastructure Affected by CVE-2025-66168?

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

Book a Demo →Browse All CVEs