CVE-2026-101117

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

GHSA-rvqc-fg65-5cq4 ↗EUVD-2026-119618 ↗

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 Extreme Scale >= 8.6.1.0, <= 8.6.2.2
CWE-16
ETK-2026-3901Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 13h 59msince last run
21mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h38m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

WebSphere Extreme Scale versions 8.6.1.0 through 8.6.2.2 are affected by an improper Content Security Policy configuration. A remote attacker could bypass security restrictions when an affected deployment is reachable remotely.

mitigation

Restrict remote access to affected WebSphere Extreme Scale deployments and review Content Security Policy configuration. Consult IBM for supported remediation; no fixed version is recorded in the 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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.40%34th percentile
agent run time
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-08 16:08Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-08 16:08Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3901",
  "cve_id": "CVE-2026-101117",
  "display_id": "CVE-2026-101117",
  "ghsa_id": "GHSA-rvqc-fg65-5cq4",
  "euvd_id": "EUVD-2026-119618",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper Content Security Policy configuration in WebSphere Extreme Scale",
  "summary": "WebSphere Extreme Scale versions 8.6.1.0 through 8.6.2.2 are affected by an improper Content Security Policy configuration. A remote attacker could bypass security restrictions when an affected deployment is reachable remotely.",
  "mitigation": "Restrict remote access to affected WebSphere Extreme Scale deployments and review Content Security Policy configuration. Consult IBM for supported remediation; no fixed version is recorded in the advisory data.",
  "vendor": "IBM",
  "product": "WebSphere Extreme Scale",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.6.1.0, <= 8.6.2.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "WebSphere Extreme Scale",
      "purl": null
    }
  ],
  "cwes": [
    16
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.004,
  "epss_percentile": 0.3446,
  "epss_asof": "2026-11-09",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 21.460516866666666,
  "t0_at": "2026-11-08T16:08:41.893000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-08T16:08:41.893000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-08T16:08:41.893000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-101117"
    }
  }
}

published 2026-11-08 16:24Z
last change 2026-11-11 05:47Z

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.