dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-51947

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A critical remote code execution vulnerability in Pivotal.Engine.Client.Services.Conversion.dll in Pivotal CRM allows remote attackers to execute arbitrary code through deserialization of untrusted data (CWE-502). This vulnerability affects version 6.6.4.08 and represents an incomplete fix for the previously reported CVE-2026-39253.

MitigationApply the vendor-supplied patch Patch_CWE502_20260316.zip or upgrade to Pivotal CRM version 6.6.5.10 to remediate the deserialization vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vulnerable DLL
    Search for Pivotal.Engine.Client.Services.Conversion.dll on the system. Typical paths include the Pivotal CRM installation directory (for example, in the bin or server subdirectories). Use a file search or check the application's bin folder.
    Affected if The DLL exists on the system, indicating Pivotal CRM components are installed.
  2. Determine the DLL file version
    Right-click the DLL file, select Properties, and check the File Version attribute on the Details tab. Alternatively, use PowerShell: (Get-Item 'C:\Path\To\Pivotal.Engine.Client.Services.Conversion.dll').VersionInfo.FileVersion
    Affected if The file version is 6.6.4.08, matching the affected version listed in the CVE.
  3. Confirm Pivotal CRM application version
    Check the installed Pivotal CRM version through the application (Help > About) or by inspecting the installation metadata. Look for version 6.6.4.08 specifically.
    Affected if The installed Pivotal CRM version is 6.6.4.08.
  4. Verify the deserialization service is accessible
    Review application configuration files (such as web.config or app.config in the application root) for endpoints or services that invoke Pivotal.Engine.Client.Services.Conversion.dll. Check for exposed web service endpoints or remoting configurations that accept serialized data.
    Affected if The application exposes a service endpoint that uses the Conversion.dll for deserializing input data, making it reachable for exploitation.

A system is affected if Pivotal.Engine.Client.Services.Conversion.dll is present with version 6.6.4.08 or if the Pivotal CRM installation is version 6.6.4.08 and the deserialization service is accessible to external callers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patch Patch_CWE502_20260316.zip or upgrade to Pivotal CRM version 6.6.5.10 to remediate the deserialization vulnerability.

Recommended fix High confidence

Pivotal CRM 6.6.5.10

  1. Identify the current installed version of Pivotal CRM by checking the system information or application metadata
  2. If running Pivotal CRM 6.6.4.08 or using patch-ghi-15381-cwe-502-20251225.zip, plan an upgrade to Pivotal CRM 6.6.5.10
  3. Apply the upgrade to Pivotal CRM version 6.6.5.10, or alternatively apply Patch_CWE502_20260316.zip as a patch-based remediation
  4. After upgrade/patch application, verify the Pivotal.Engine.Client.Services.Conversion.dll component has been updated to the fixed version
  5. Confirm the new version is reflected in the system (e.g., About page, version check)
  6. Test critical business functions to ensure the system operates normally post-upgrade
Caveat Test all custom integrations and workflows after upgrade, as deserialization fixes may affect data processing behavior

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-51947 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-51947 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data