Affects IBM DataPower Gateway — a widely deployed enterprise API gateway; signature verification bypass can enable broad unauthorized access across organizations.
CVE-2026-14497
Authenticated crypto-signature bypass in IBM DataPower Gateway
Is CVE-2026-14497 being exploited?
Not confirmed. CVE-2026-14497 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.59% probability of exploitation in the next 30 days.
How severe is CVE-2026-14497?
CVE-2026-14497 is rated High with a CVSS score of 8.1. 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-14497?
Not known from our data. No patch reference has been recorded for CVE-2026-14497, 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-14497 affect?
CVE-2026-14497 affects IBM DataPower Gateway 10.5.0.0 - 10.5.0.22, IBM DataPower Gateway 10.6.0.0 - 10.6.0.10, IBM DataPower Gateway 10.6.1 - 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-14497?
Apply vendor guidance, restrict management/API access, rotate keys, monitor logs
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote authenticated attacker can bypass signature checks to gain unauthorized access, perform privileged actions, or tamper with signed data.
Patch when possible
- 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.