CVE-2026-50632

CRITICALPre-NVD 8.19.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-12. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 1.7.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A further incomplete fix for a previous advisory CVE-2026-44417 (Untrusted JMS configuration can lead to RCE) for Apache CXF has been identified, which can allow code execution capabilities, if untrusted users are allowed to configure JMS for Apache CXF. Users are recommended to upgrade to versions 4.2.2 or 4.1.7 or 3.6.12, which fixes this issue.

CVSS v3
8.1
EG Score
9.8CRITICALmedium confidence
EG Risk
44
EG Risk 44/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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
1.1%
EPSS %ILE
65th
KEV
Not listed

Published

June 12, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Jun 12, 2026
Patch available.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcxf-rt-transports-jms2026-07-09redhat

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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFix by version rangeDependents
org.apache.cxf:cxf-rt-transports-jms2.0.10 ... 4.1.6 (226 versions)
  • 4.2.0 up to 4.2.2: fixed in 4.2.2
  • every version up to 4.1.7: fixed in 4.1.7
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-50632?
CVE-2026-50632 is a critical vulnerability published on June 12, 2026. A further incomplete fix for a previous advisory CVE-2026-44417 (Untrusted JMS configuration can lead to RCE) for Apache CXF has been identified, which can allow code execution capabilities, if untrusted users are allowed to configure JMS for Apache CXF. Users are recommended to upgrade to versions…
When was CVE-2026-50632 disclosed?
CVE-2026-50632 was first published on June 12, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50632 actively exploited?
CVE-2026-50632 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (65th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-50632?
CVE-2026-50632 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2026-50632?
A fix for CVE-2026-50632 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-50632 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-50632

Explore →

Is Your Infrastructure Affected by CVE-2026-50632?

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