CVE-2026-51947

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-01. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.1%CVSS: 9.8Exploit: None knownExposed services: Not assessed

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

An issue in Pivotal CRM 6.6.4.08 and systems using patch-ghi-15381-cwe-502-20251225.zip (fixed in Pivotal CRM 6.6.5.10 and Patch_CWE502_20260316.zip) allows a remote attacker to execute arbitrary code via the Pivotal.Engine.Client.Services.Conversion.dll component. NOTE: this issue exists because of an incomplete fix for CVE-2026-39253.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
60
EG Risk 60/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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation1.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.1%
EPSS %ILE
64th
KEV
Not listed

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (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

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (3)

Auto-updated Oct 11, 2026
No fix on record yet.
Web page

CVE-2026-51947: Incomplete Deserialisation Patch in Pivotal CRM

https://timtimxs.github.io/CVE-2026-51947-Advisory/
Web page

Remediating Insecure Deserialization (CWE-502) in Pivotal 6.6.04.08 (Smart Client / PBS) - Pivotal Support

https://timtimxs.github.io/CVE-2026-39253-Advisory/
Web page

Sign in - Pivotal Support

https://support.pivotal.aurea.com/article/129552-remediating-insecure-deserialization-cwe-502-in-pivotal-6-6-04-08-smart-client-pbs

Vendor Advisories for CVE-2026-51947(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 17× in last 7d / 39× 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 391 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 291 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-51947?
CVE-2026-51947 is a critical-severity vulnerability; its CVE record was published on July 1, 2026. An issue in Pivotal CRM 6.6.4.08 and systems using patch-ghi-15381-cwe-502-20251225.zip (fixed in Pivotal CRM 6.6.5.10 and PatchCWE50220260316.zip) allows a remote attacker to execute arbitrary code via the Pivotal.Engine.Client.Services.Conversion.dll component. NOTE: this issue exists because of…
When was the CVE record for CVE-2026-51947 published?
The CVE record for CVE-2026-51947 was published on July 1, 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 July 2, 2026; the record at its source may have been updated since.
Is CVE-2026-51947 actively exploited?
CVE-2026-51947 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.1% probability of exploitation in the next 30 days (64th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-51947?
CVE-2026-51947 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-51947?
No fix for CVE-2026-51947 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-51947 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-51947

Explore →

Is Your Infrastructure Affected by CVE-2026-51947?

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

Book a Demo →Browse All CVEs