CVE-2026-47168

waiting for further signalsZero needs more public information before it can validate it.

GHSA-7q78-jjr9-mqcg ↗EUVD-2026-102096 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
espocrm <= 9.3.6
fixed in 9.3.7
CWE-502 Deserialization of Untrusted Data
ETK-2026-1689Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:composer/espocrm/espocrm
5d 13h 24msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h38m
0
+4h
+6h
+8h
+10h
+12h

description

EspoCRM versions before 9.3.7 mishandle serialized PHP object data stored for background MassAction or Export jobs. An authenticated administrator can cause server-side code execution when the affected data is later processed.

mitigation

Upgrade EspoCRM to version 9.3.7 or later. Restrict administrator access until the update is complete.

fixed in 9.3.7

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.42%35th percentile
agent run time
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-15 14:42Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-15 14:42Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-47168

{
  "etk_id": "ETK-2026-1689",
  "cve_id": "CVE-2026-47168",
  "display_id": "CVE-2026-47168",
  "ghsa_id": "GHSA-7q78-jjr9-mqcg",
  "euvd_id": "EUVD-2026-102096",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unsafe PHP object deserialization in EspoCRM",
  "summary": "EspoCRM versions before 9.3.7 mishandle serialized PHP object data stored for background MassAction or Export jobs. An authenticated administrator can cause server-side code execution when the affected data is later processed.",
  "mitigation": "Upgrade EspoCRM to version 9.3.7 or later. Restrict administrator access until the update is complete.",
  "vendor": "espocrm",
  "product": "espocrm",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 9.3.6"
      ],
      "ecosystem": "composer",
      "fixed_versions": [
        "9.3.7"
      ],
      "package_name": "espocrm/espocrm",
      "purl": "pkg:composer/espocrm/espocrm"
    }
  ],
  "cwes": [
    502
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0042,
  "epss_percentile": 0.3525,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.34675635,
  "t0_at": "2026-10-15T14:42:15.975000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-15T14:42:15.975000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-15T14:42:15.975000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-47168"
    }
  }
}

published 2026-10-15 15:44Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.