CVE-2025-64393

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

GHSA-6m95-66x2-x5hx ↗EUVD-2025-211039 ↗

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.
veeam Backup and Replication >= 12, < 12.3.2.4934
fixed in 12.3.2.4934
ETK-2026-863, permanent identifier
14d 11h 42msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h17m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Veeam Backup & Replication is affected by an unsafe deserialization issue. An attacker with Backup Viewer access could run code with SYSTEM-level privileges on the backup server; this requires access to an account assigned that role.

mitigation

Upgrade Backup and Replication to 12.3.2.4934 or later.

fixed in 12.3.2.4934

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, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.36%28th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 08:48Z
Δ 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-07 08:48Z
    ghsa: trigger signal, started the run
  2. 2026-10-07 08:48Z

this entry in the feed

GET /api/v1/feed/CVE-2025-64393

{
  "etk_id": "ETK-2026-863",
  "cve_id": "CVE-2025-64393",
  "display_id": "CVE-2025-64393",
  "ghsa_id": "GHSA-6m95-66x2-x5hx",
  "euvd_id": "EUVD-2025-211039",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unsafe deserialization in Veeam Backup & Replication",
  "summary": "Veeam Backup & Replication is affected by an unsafe deserialization issue. An attacker with Backup Viewer access could run code with SYSTEM-level privileges on the backup server; this requires access to an account assigned that role.",
  "mitigation": "Upgrade Backup and Replication to 12.3.2.4934 or later.",
  "vendor": "veeam",
  "product": "Backup and Replication",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12, < 12.3.2.4934"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "12.3.2.4934"
      ],
      "package_name": "Backup and Replication",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
  "epss_score": 0.0036,
  "epss_percentile": 0.2834,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.96824575,
  "t0_at": "2026-10-07T08:48:49.509000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-07T08:48:49.509000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T08:48:49.509000+00:00",
      "url": "https://github.com/advisories/GHSA-6m95-66x2-x5hx"
    }
  }
}

published 2026-10-07 09:53Z
last change 2026-10-21 18:17Z

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.