CVE-2026-44839

MEDIUMNVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% 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
Trending — 4 sources updated this week
4.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.8Exploit: None knownExposed: 0

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

RabbitMQ is a messaging and streaming broker. From 3.7.0 to before 4.1.2 and 4.0.13, This vulnerability is fixed in 4.1.2 and 4.0.13.

CVSS v3
4.8
EG Score
4.8(medium)
EG Risk
22(Track)
EG Risk 22/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
Severity48% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 4, 2026

Advisory Details (2)

Auto-updated Jun 17, 2026
Patch available. Sources: github_commit, github.
github Patch Available

Unsanitized vhost names allow for XSS in management UI · Advisory · rabbitmq/rabbitmq-server · GitHub

https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-fh5r-jpm3-fjwp
github_commit

commit 7f54319279d1 (rabbitmq/rabbitmq-server)

Fix landed in rabbitmq/rabbitmq-server commit 7f54319279d1 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-server/commit/7f54319279d1ece161ae0b4cdc6f0e58a4045eb5

Vendor Advisories for CVE-2026-44839(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server3.10.8-1 ... 4.3.2-4 (38 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server3.10.8-1.1 ... 4.3.2-4 (27 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server4.0.5-10 ... 4.3.2-4 (17 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
rabbitmq-server4.0.5-10 ... 4.3.0-1 (9 versions)4.3.0-2—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44839?
CVE-2026-44839 is a medium vulnerability published on May 27, 2026. RabbitMQ is a messaging and streaming broker. From 3.7.0 to before 4.1.2 and 4.0.13, This vulnerability is fixed in 4.1.2 and 4.0.13.
When was CVE-2026-44839 disclosed?
CVE-2026-44839 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44839 actively exploited?
CVE-2026-44839 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.2% of all scored CVEs.
What is the CVSS score of CVE-2026-44839?
CVE-2026-44839 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-44839?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44839, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44839

Explore →

Is Your Infrastructure Affected by CVE-2026-44839?

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

Start Free Scan →Browse All CVEs