CVE-2026-95695

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

GHSA-pxc5-x8x9-34qq ↗EUVD-2026-100496 ↗

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 WebSphere Application Server - Liberty >= 20.0.0.12, <= 26.0.0.10
ETK-2026-1890Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 22h 10msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+91h08m
0
+2h
+4h
+6h
+8h
+10h

description

WebSphere Application Server Liberty versions 20.0.0.12 through 26.0.0.10 are affected by an authorization flaw. A remote attacker may be able to bypass security restrictions; the evidence does not describe the deployment-specific conditions required.

mitigation

Apply IBM's security update guidance for Liberty; the supplied evidence does not identify a fixed version. Until updates are deployed, restrict network access to affected Liberty instances to trusted clients and networks.

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.33%24th percentile
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 20:17Z
Δ 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-13 20:17Z
    ghsa: trigger signal, started the run
  2. 2026-10-13 20:17Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1890",
  "cve_id": "CVE-2026-95695",
  "display_id": "CVE-2026-95695",
  "ghsa_id": "GHSA-pxc5-x8x9-34qq",
  "euvd_id": "EUVD-2026-100496",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authorization bypass in WebSphere Application Server Liberty",
  "summary": "WebSphere Application Server Liberty versions 20.0.0.12 through 26.0.0.10 are affected by an authorization flaw. A remote attacker may be able to bypass security restrictions; the evidence does not describe the deployment-specific conditions required.",
  "mitigation": "Apply IBM's security update guidance for Liberty; the supplied evidence does not identify a fixed version. Until updates are deployed, restrict network access to affected Liberty instances to trusted clients and networks.",
  "vendor": "IBM",
  "product": "WebSphere Application Server - Liberty",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 20.0.0.12, <= 26.0.0.10"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WebSphere Application Server - Liberty",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0033,
  "epss_percentile": 0.247,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.0296392,
  "t0_at": "2026-10-13T20:17:53.799000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-13T20:17:53.799000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T20:17:53.799000+00:00",
      "url": "https://github.com/advisories/GHSA-pxc5-x8x9-34qq"
    }
  }
}

published 2026-10-17 15:04Z
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.