CVE-2026-63336

MEDIUMPre-NVD 5.15.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (23rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-61045 (ENISA EUVD) · GHSA-5m9f-rphj-c435 (GitHub Security Advisories)Source: ENISA EUVD

5.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, com.rabbitmq.client.ConnectionFactory.useSslProtocol() and ConnectionFactory.useSslProtocol(String) configure com.rabbitmq.client.TrustEverythingTrustManager and leave hostname verification disabled, causing arbitrary server certificates, including self-signed certificates, to be accepted. A network attacker able to intercept a TLS connection can impersonate the RabbitMQ broker, read protected AMQP traffic, and modify traffic without certificate or hostname validation. The fix changes the production TLS helpers to use the JVM default trust store and enables hostname verification, while retaining an explicitly named development-only no-verification helper. This issue is fixed in version 5.33.0.

CVSS v3
5.1
EG Score
5.1MEDIUMmedium confidence
EG Risk
39
EG Risk 39/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity51% × 45%
Impact severity (EG Severity): CVSS 5.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.1): severity, escalated by confirmed exploitation. This CVE's 5.1 is its impact severity (EG Severity), not escalated.

EG Severity
5.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 18, 2026

Last Modified

October 22, 2026

Advisory Details (6)

Auto-updated Aug 18, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

5.33.0

Patch available: rabbitmq/rabbitmq-java-client v5.33.0

https://github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0
GitHub commit

commit a4bf571dd368 (rabbitmq/rabbitmq-java-client)

Fix landed in rabbitmq/rabbitmq-java-client commit a4bf571dd368 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-java-client/commit/a4bf571dd368765baaa9cecfae68ce09f1bdcc01
GitHub commit Patch Available

commit 1e7deb2e6020 (rabbitmq/rabbitmq-java-client)

Patch available: rabbitmq/rabbitmq-java-client v5.33.0 (contains commit 1e7deb2e6020)

https://github.com/rabbitmq/rabbitmq-java-client/commit/1e7deb2e6020c9793a81385a53ea378ec63b9339
GitHub pull request Patch Available

Introduce helper for dev/test TLS setup (backport #1999)

Patch available: rabbitmq/rabbitmq-java-client v5.33.0 (PR #2001 merged 2026-06-30)

https://github.com/rabbitmq/rabbitmq-java-client/pull/2001
GitHub pull request

Introduce helper for dev/test TLS setup

Fix merged in rabbitmq/rabbitmq-java-client PR #1999 on 2026-06-29 — awaiting tagged release

https://github.com/rabbitmq/rabbitmq-java-client/pull/1999
GitHub advisoryMentions a patch (unverified)

TrustEverythingTrustManager used by default in useSslProtocol() enables MITM · Advisory · rabbitmq/rabbitmq-java-client · GitHub

https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5m9f-rphj-c435

Vendor Advisories for CVE-2026-63336(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavencom.rabbitmq:amqp-client @ 5.33.0 (fixes < 5.33.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-java-client5.0.0-1.1, 5.0.0-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-java-client5.0.0-1.1, 5.0.0-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rabbitmq-java-client5.0.0-1.1, 5.0.0-2
  • every version on: no fix on record
—
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
com.rabbitmq:amqp-client1.3.0 ... 5.9.0 (150 versions)
  • every version up to 5.33.0: fixed in 5.33.0
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 117 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 17 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-63336?
CVE-2026-63336 is a medium-severity vulnerability; its CVE record was published on August 18, 2026. The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, com.rabbitmq.client.ConnectionFactory.useSslProtocol() and ConnectionFactory.useSslProtocol(String) configure com.rabbitmq.client.TrustEverythingTrustManager and…
When was the CVE record for CVE-2026-63336 published?
The CVE record for CVE-2026-63336 was published on August 18, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-63336 actively exploited?
CVE-2026-63336 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63336?
CVE-2026-63336 has a CVSS base score of 5.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-63336?
A fix for CVE-2026-63336 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63336 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-63336?

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