CVE-2026-19622

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

GHSA-73c5-qf5f-mp9w ↗EUVD-2026-98078 ↗

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-288 Authentication Bypass Using an Alternate Path or Channel
ETK-2026-1434Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 05h 21msince last run
18mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h43m
0
+4h
+6h
+8h
+10h
+12h

description

IBM Planning Analytics 2.0 and 2.1 are affected by improper validation of sub-requests. A remote attacker may bypass authentication and obtain elevated privileges; the advisory does not state additional preconditions.

mitigation

Restrict remote access to Planning Analytics to trusted users and networks while awaiting vendor guidance. Apply an IBM-provided update when one is 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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.34%26th percentile
agent run time
18m
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-19622

{
  "etk_id": "ETK-2026-1434",
  "cve_id": "CVE-2026-19622",
  "display_id": "CVE-2026-19622",
  "ghsa_id": "GHSA-73c5-qf5f-mp9w",
  "euvd_id": "EUVD-2026-98078",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass and privilege escalation in Planning Analytics",
  "summary": "IBM Planning Analytics 2.0 and 2.1 are affected by improper validation of sub-requests. A remote attacker may bypass authentication and obtain elevated privileges; the advisory does not state additional preconditions.",
  "mitigation": "Restrict remote access to Planning Analytics to trusted users and networks while awaiting vendor guidance. Apply an IBM-provided update when one is 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": [
    288
  ],
  "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": 0.0034,
  "epss_percentile": 0.2629,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 18.322447966666665,
  "t0_at": "2026-10-12T22:40:20.049000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T22:40:20.049000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T22:40:20.049000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-19622"
    }
  }
}

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