← back to feed
CVE-2026-86398

CVE-2026-86398

validatedZero produced an exploit or a check.

GHSA-h3p7-cf5p-3mr2 ↗EUVD-2026-111840 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Dell PowerProtect Data Domain >= 0, < 8.9.0.0 or later; >= 0, < 7.13.1.90 or later; >= 0, < 8.3.1.50 or later; >= 0, < 8.6.1.30 or later
fixed in 8.9.0.0 or later, 7.13.1.90 or later, 8.3.1.50 or later, 8.6.1.30 or later
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-2848Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss8.8cna vendorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
+26mTTV
12mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0mcheck available+26magent stopped
0
+5min
+10min
+15min
+20min

description

Dell PowerProtect Data Domain Feature Release 7.7.1.0 through 8.8 and affected LTS release trains are vulnerable to path traversal. A remote attacker with low-privileged access may reach filesystem locations outside the intended directory scope.

mitigation

Upgrade to 8.9.0.0 or later, 7.13.1.90 or later, 8.3.1.50 or later, or 8.6.1.30 or later, as applicable. Until upgraded, restrict remote access and limit low-privileged account access.

fixed in 8.9.0.0 or later, 7.13.1.90 or later, 8.3.1.50 or later, 8.6.1.30 or later

check
available
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.
–
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-28 08:58Z
Δ 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 check: a technique exists and was validated, 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-28 08:58Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-86398

this entry in the feed

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

{
  "etk_id": "ETK-2026-2848",
  "cve_id": "CVE-2026-86398",
  "display_id": "CVE-2026-86398",
  "ghsa_id": "GHSA-h3p7-cf5p-3mr2",
  "euvd_id": "EUVD-2026-111840",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Dell PowerProtect Data Domain",
  "summary": "Dell PowerProtect Data Domain Feature Release 7.7.1.0 through 8.8 and affected LTS release trains are vulnerable to path traversal. A remote attacker with low-privileged access may reach filesystem locations outside the intended directory scope.",
  "mitigation": "Upgrade to 8.9.0.0 or later, 7.13.1.90 or later, 8.3.1.50 or later, or 8.6.1.30 or later, as applicable. Until upgraded, restrict remote access and limit low-privileged account access.",
  "vendor": "Dell",
  "product": "PowerProtect Data Domain",
  "affected": [
    {
      "affected_notes": [
        ">= 0, < 8.9.0.0 or later",
        ">= 0, < 7.13.1.90 or later",
        ">= 0, < 8.3.1.50 or later",
        ">= 0, < 8.6.1.30 or later"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "8.9.0.0 or later",
        "7.13.1.90 or later",
        "8.3.1.50 or later",
        "8.6.1.30 or later"
      ],
      "package_name": "PowerProtect Data Domain",
      "purl": null
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 12.4285929,
  "t0_at": "2026-10-28T08:58:15.053000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-28T09:24:28.026329+00:00",
      "days": 0.01820570982638889,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T08:58:15.053000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-28T08:58:15.053000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-28T08:58:15.053000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-86398"
    }
  }
}

published 2026-10-28 09:04Z
last change 2026-10-28 14:32Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.