CVE-2026-82101

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

GHSA-xw9r-68jj-g9xg ↗EUVD-2026-98072 ↗

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 DataStage on Cloud Pak for Data 5.4.0.0
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-1430Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 04h 51msince 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+2h27m
0
+4h
+6h
+8h
+10h
+12h

description

IBM DataStage on Cloud Pak for Data 5.4.0.0 is affected by a path traversal vulnerability. An authenticated remote attacker may be able to cause a denial of service; access to an authenticated account is required.

mitigation

Restrict access to authenticated DataStage accounts to trusted users and networks, and monitor for the vendor's remediation guidance. No fixed version is recorded in the available advisory data.

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.41%33rd percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 22:26Z
Δ 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-12 22:26Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1430",
  "cve_id": "CVE-2026-82101",
  "display_id": "CVE-2026-82101",
  "ghsa_id": "GHSA-xw9r-68jj-g9xg",
  "euvd_id": "EUVD-2026-98072",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authenticated path traversal in DataStage on Cloud Pak for Data",
  "summary": "IBM DataStage on Cloud Pak for Data 5.4.0.0 is affected by a path traversal vulnerability. An authenticated remote attacker may be able to cause a denial of service; access to an authenticated account is required.",
  "mitigation": "Restrict access to authenticated DataStage accounts to trusted users and networks, and monitor for the vendor's remediation guidance. No fixed version is recorded in the available advisory data.",
  "vendor": "IBM",
  "product": "DataStage on Cloud Pak for Data",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "5.4.0.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DataStage on Cloud Pak for Data",
      "purl": null
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 9.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H",
  "epss_score": 0.0041,
  "epss_percentile": 0.3365,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.96172665,
  "t0_at": "2026-10-12T22:26:35.727000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T22:26:35.727000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T22:26:35.727000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-82101"
    }
  }
}

published 2026-10-12 23:31Z
last change 2026-10-21 05:31Z

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.