CVE-2026-16163

validatedZero produced an exploit or a check.

GHSA-w4qj-mcfp-cvf5 ↗EUVD-2026-94963 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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 DataPower Gateway 10.6CD >= 10.6.1, <= 10.6.6; >= 10.6.0.0, <= 10.6.0.10; >= 11.0.0.0, <= 11.0.0.2; >= 10.5.0.0, <= 10.5.0.22
CWE-787 Out-of-bounds Write
ETK-2026-987, permanent identifier
+2.5dTTV
12mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0dcheck available+2.5dagent stopped
0
+1d
+2d

description

IBM DataPower Gateway 10.5.0.0–10.5.0.22, 10.6.0.0–10.6.0.10, 10.6.1–10.6.6, and 11.0.0.0–11.0.0.2 are affected. A remote attacker able to reach a vulnerable gateway may trigger memory corruption.

mitigation

Restrict network access to affected gateways to trusted sources and limit exposure of their reachable services. Monitor IBM guidance and apply a vendor-provided update when one is available; no fixed version is recorded in the advisory.

check
available
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.27%18th percentile
agent run time
12m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-08 13:20Z
Δ 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 check: a technique exists and was validated, 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-08 13:20Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-987",
  "cve_id": "CVE-2026-16163",
  "display_id": "CVE-2026-16163",
  "ghsa_id": "GHSA-w4qj-mcfp-cvf5",
  "euvd_id": "EUVD-2026-94963",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds write in IBM DataPower Gateway",
  "summary": "IBM DataPower Gateway 10.5.0.0–10.5.0.22, 10.6.0.0–10.6.0.10, 10.6.1–10.6.6, and 11.0.0.0–11.0.0.2 are affected. A remote attacker able to reach a vulnerable gateway may trigger memory corruption.",
  "mitigation": "Restrict network access to affected gateways to trusted sources and limit exposure of their reachable services. Monitor IBM guidance and apply a vendor-provided update when one is available; no fixed version is recorded in the advisory.",
  "vendor": "IBM",
  "product": "DataPower Gateway 10.6CD",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.6.1, <= 10.6.6"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DataPower Gateway 10.6CD",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.6.0.0, <= 10.6.0.10"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DataPower Gateway 10.6.0",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 11.0.0.0, <= 11.0.0.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DataPower Gateway 11.0.0",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 10.5.0.0, <= 10.5.0.22"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "DataPower Gateway 10.5.0",
      "purl": null
    }
  ],
  "cwes": [
    787
  ],
  "cvss_score": 8.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H",
  "epss_score": 0.0027,
  "epss_percentile": 0.1855,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 11.518257683333333,
  "t0_at": "2026-10-08T13:20:11.794000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-11T01:36:05.275421+00:00",
      "days": 2.5110356645949072,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T13:20:11.794000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-08T13:20:11.794000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-08T13:20:11.794000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-16163"
    }
  }
}

published 2026-10-08 15:39Z
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.