CVE-2026-75875

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

GHSA-qwfw-cq7q-5365 ↗EUVD-2026-95339 ↗

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.
ibm Guardium Data Protection 12.0; 12.1; 12.2
ETK-2026-1022Zero's internal tracking ID, independent of the CVE number., permanent identifier
12d 02h 58msince last run
7mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h20m
0
+2h
+6h
+8h
+10h
+12h

description

Guardium Data Protection versions 12.0, 12.1, and 12.2 are affected by a path-traversal issue. A remote attacker could execute arbitrary code; the available advisory text does not identify additional preconditions.

mitigation

Restrict network access to affected Guardium Data Protection deployments to trusted administrative users and networks. Obtain and apply the vendor's remediation; the evidence does not specify a fixed version.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1022",
  "cve_id": "CVE-2026-75875",
  "display_id": "CVE-2026-75875",
  "ghsa_id": "GHSA-qwfw-cq7q-5365",
  "euvd_id": "EUVD-2026-95339",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Guardium Data Protection",
  "summary": "Guardium Data Protection versions 12.0, 12.1, and 12.2 are affected by a path-traversal issue. A remote attacker could execute arbitrary code; the available advisory text does not identify additional preconditions.",
  "mitigation": "Restrict network access to affected Guardium Data Protection deployments to trusted administrative users and networks. Obtain and apply the vendor's remediation; the evidence does not specify a fixed version.",
  "vendor": "ibm",
  "product": "Guardium Data Protection",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "12.0",
        "12.1",
        "12.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Guardium Data Protection",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0058,
  "epss_percentile": 0.467,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 7.415885066666667,
  "t0_at": "2026-10-08T21:29:46.266000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-08T21:29:46.266000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T21:29:46.266000+00:00",
      "url": "https://github.com/advisories/GHSA-qwfw-cq7q-5365"
    }
  }
}

published 2026-10-09 01:42Z
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.