CVE-2026-10538

HIGHPre-NVD 8.08.0
EchelonGraph scoreHIGH confidence

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

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

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

Messaging consumer functionality allows deserialization of user-controlled data without sufficient restriction of allowed object types in the out of support Control-M/Server and Control-M/Enterprise Manager versions 9.0.20.x and potentially earlier. This issue may allow an authenticated attacker to trigger unintended server-side behavior through crafted serialized content.

CVSS v3
8.0
EG Score
8.0(high)
EG Risk
41(Track)
EG Risk 41/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
Severity80% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 1, 2026

Advisory Details (1)

Auto-updated Jul 1, 2026
No patch confirmed yet.
generic

CVE-2026-10538 detected on Control-M/Enterprise Manager 9.0.20: Improper Deserialization Handling in Control-M Components

https://bmcapps.my.site.com/casemgmt/sc_KnowledgeArticle?sfdcid=kA3cx000000GFKrCAO&type=Solution

Vendor Advisories for CVE-2026-10538(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 64× 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.

  1. 2026-07-27 02:23 UTCEG score recompute
  2. 2026-07-27 02:23 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 13:29 UTCEG score recompute
  6. 2026-07-26 13:29 UTCGHSA enrichment
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:04 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 14:30 UTCEPSS rescore
  15. 2026-07-19 02:28 UTCEPSS rescore
  16. 2026-07-18 10:04 UTCEPSS rescore
  17. 2026-07-16 23:12 UTCGHSA enrichment
  18. 2026-07-16 17:02 UTCEPSS rescore
  19. 2026-07-16 10:20 UTCGHSA enrichment
  20. 2026-07-15 21:27 UTCGHSA enrichment
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 08:33 UTCGHSA enrichment
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-14 19:39 UTCGHSA enrichment
  25. 2026-07-14 06:46 UTCGHSA enrichment
Show 39 more
  1. 2026-07-13 22:30 UTCEPSS rescore
  2. 2026-07-13 17:51 UTCGHSA enrichment
  3. 2026-07-13 06:12 UTCEPSS rescore
  4. 2026-07-13 04:58 UTCGHSA enrichment
  5. 2026-07-12 16:06 UTCGHSA enrichment
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-12 03:13 UTCGHSA enrichment
  8. 2026-07-11 14:21 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-11 01:29 UTCGHSA enrichment
  11. 2026-07-10 12:35 UTCGHSA enrichment
  12. 2026-07-09 23:43 UTCGHSA enrichment
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-09 10:50 UTCGHSA enrichment
  15. 2026-07-08 21:56 UTCGHSA enrichment
  16. 2026-07-08 15:15 UTCEPSS rescore
  17. 2026-07-08 15:15 UTCEPSS rescore
  18. 2026-07-08 09:03 UTCGHSA enrichment
  19. 2026-07-07 20:11 UTCGHSA enrichment
  20. 2026-07-07 13:46 UTCEPSS rescore
  21. 2026-07-07 07:17 UTCGHSA enrichment
  22. 2026-07-06 18:16 UTCGHSA enrichment
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 05:23 UTCGHSA enrichment
  25. 2026-07-06 02:23 UTCEPSS rescore
  26. 2026-07-05 16:29 UTCGHSA enrichment
  27. 2026-07-05 03:36 UTCGHSA enrichment
  28. 2026-07-05 02:30 UTCEPSS rescore
  29. 2026-07-05 02:30 UTCEPSS rescore
  30. 2026-07-04 14:42 UTCGHSA enrichment
  31. 2026-07-04 01:50 UTCGHSA enrichment
  32. 2026-07-03 12:57 UTCGHSA enrichment
  33. 2026-07-03 00:05 UTCGHSA enrichment
  34. 2026-07-02 11:11 UTCGHSA enrichment
  35. 2026-07-01 22:18 UTCGHSA enrichment
  36. 2026-07-01 15:06 UTCEPSS rescore
  37. 2026-07-01 15:06 UTCEPSS rescore
  38. 2026-07-01 09:23 UTCEG score recompute
  39. 2026-07-01 09:22 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-10538?
CVE-2026-10538 is a high vulnerability published on July 1, 2026. Messaging consumer functionality allows deserialization of user-controlled data without sufficient restriction of allowed object types in the out of support Control-M/Server and Control-M/Enterprise Manager versions 9.0.20.x and potentially earlier. This issue may allow an authenticated attacker to…
When was CVE-2026-10538 disclosed?
CVE-2026-10538 was first published in the National Vulnerability Database on July 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-10538 actively exploited?
CVE-2026-10538 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 84.0% of all scored CVEs.
What is the CVSS score of CVE-2026-10538?
CVE-2026-10538 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-10538?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-10538, 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-10538

Explore →

Is Your Infrastructure Affected by CVE-2026-10538?

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