IBM DataPower is a widely deployed enterprise API/gateway appliance; remote RCE in it can lead to large-scale compromise and service disruption.
CVE-2026-16340
Remote RCE in IBM DataPower via RFC2047 parser
Is CVE-2026-16340 being exploited?
Not confirmed. CVE-2026-16340 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-16340?
CVE-2026-16340 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-16340?
Not known from our data. No patch reference has been recorded for CVE-2026-16340, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-16340 affect?
CVE-2026-16340 affects IBM DataPower Gateway 10.5.0.0 - 10.5.0.22, IBM DataPower Gateway 10.6.0.0 - 10.6.6, IBM DataPower Gateway 11.0.0.0 - 11.0.0.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16340?
Isolate affected appliances and apply vendor updates or mitigations immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution enabling full appliance takeover via crafted RFC2047 encoded-word input.
Immediate action required
- affected>= 10.5.0.0 and <= 10.5.0.22
- affected>= 10.6.0.0 and <= 10.6.0.10
- affected>= 10.6.1 and <= 10.6.6
- affected>= 11.0.0.0 and <= 11.0.0.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.