Cyber & AI intelligence
Wasteland.
Briefs indexed3586
Issues35
Published Mondays07:30 CT
⚡ Active KEV CVE-2026-101117 2026-11-08

CVE-2026-101117: Critical Security Bypass in IBM WebSphere Extreme Scale

"IBM WebSphere Extreme Scale 8.6.1.0 through 8.6.2.2 has a critical-rated (CVSS 9.1) flaw: an improperly configured Content Security Policy could let a remote, unauthenticated attacker bypass security restrictions."

IBM WebSphere Extreme Scale 8.6.1.0 through 8.6.2.2 has a critical-rated (CVSS 9.1) flaw: an improperly configured Content Security Policy could let a remote, unauthenticated attacker bypass security restrictions.

What Is It

CVE-2026-101117 is a security restriction bypass in IBM WebSphere Extreme Scale. According to IBM's PSIRT, the root cause is an improperly configured Content Security Policy (CSP). The weakness is classified as CWE-16 (Configuration).

IBM published the record on November 8, 2026. NVD lists its status as "Awaiting Analysis," so NVD has not yet published its own assessment. The available scoring and details come from IBM as the CVE source.

Why It Matters

IBM rates the vulnerability CVSS 3.1 9.1 (Critical), with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. In practice:

Exploitation status: CVE-2026-101117 is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, and the supplied data does not confirm active exploitation. Given the critical score and the low barrier to exploitation, organizations running affected versions should still prioritize it.

What's Vulnerable

The CPE entries in the record mark the endpoints of the affected range:

Patch Status

The supplied NVD data does not give a fixed version or specific remediation steps. Because the entry is not in KEV, CISA has not issued a required action or due date.

IBM has published a support page for this issue, linked below. Administrators should:

  1. Check which WebSphere Extreme Scale version they run against the affected range of 8.6.1.0 through 8.6.2.2.
  2. Follow IBM's advisory for remediation guidance and any available fix.
  3. Re-check the NVD record and the KEV catalog for updated analysis or exploitation status.

Sources