CVE-2026-19627

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

GHSA-qcr6-xqfp-3rhr ↗EUVD-2026-98075 ↗

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 Planning Analytics 2.0; 2.1
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-1439Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 05h 08msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h56m
0
+4h
+6h
+8h
+10h
+12h

description

Planning Analytics 2.0 and 2.1 contain a path-validation flaw. A remote attacker may read files on the host or alter certain application files; exploitation requires network access to an affected deployment, while authentication requirements are not specified.

mitigation

Restrict network access to affected Planning Analytics deployments and run the service with the minimum filesystem permissions needed. Monitor for and apply IBM-provided updates when available.

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

this entry in the feed

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

{
  "etk_id": "ETK-2026-1439",
  "cve_id": "CVE-2026-19627",
  "display_id": "CVE-2026-19627",
  "ghsa_id": "GHSA-qcr6-xqfp-3rhr",
  "euvd_id": "EUVD-2026-98075",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Planning Analytics",
  "summary": "Planning Analytics 2.0 and 2.1 contain a path-validation flaw. A remote attacker may read files on the host or alter certain application files; exploitation requires network access to an affected deployment, while authentication requirements are not specified.",
  "mitigation": "Restrict network access to affected Planning Analytics deployments and run the service with the minimum filesystem permissions needed. Monitor for and apply IBM-provided updates when available.",
  "vendor": "IBM",
  "product": "Planning Analytics",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "2.0",
        "2.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Planning Analytics",
      "purl": null
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N",
  "epss_score": 0.0035,
  "epss_percentile": 0.2766,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.2341294,
  "t0_at": "2026-10-12T22:40:06.613000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T22:40:06.613000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T22:40:06.613000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-19627"
    }
  }
}

published 2026-10-13 00:22Z
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.