Security Advisory: CVE-2026-34181

Uses: Kong Gateway
Published
2026-08-10
Fixed versions
  • 3.15.0.3
  • 3.14.0.12
  • 3.13.0.9
  • 3.12.0.10
  • 3.10.0.17
  • 3.4.3.29
Affected versions
  • 3.15.0.0 to 3.15.0.2
  • 3.14.0.0 to 3.14.0.11
  • 3.13.0.0 to 3.13.0.8
  • 3.12.0.0 to 3.12.0.9
  • 3.10.0.0 to 3.10.0.16
  • 3.4.0.0 to 3.4.3.28

CVE

Description

Severity

Affects Kong

CVE-2026-34181 OpenSSL accepts PKCS#12 files that use PBMAC1 with short HMAC keys No

Kong has assessed CVE-2026-34181 and found that it doesn’t affect Kong core.

CVE-2026-34181

When PKCS#12 files use PBMAC1 for integrity protection, OpenSSL may accept them even when protected by an unexpectedly short HMAC key, weakening the integrity guarantee (an attacker could forge a certificate/key bundle that passes the MAC check with ~1-in-256 probability).

Am I affected?

No in core; conditionally reachable only via a custom plugin. Kong configures TLS using PEM-format certificates and keys, not PKCS#12 (.p12) bundles, so core never parses PKCS#12. The pkcs12 module is in the plugin sandbox, so a custom plugin that imports attacker-supplied .p12 files would be exposed. No Kong core or bundled plugin parses PKCS#12.

Scenario (only if a custom plugin imports PKCS#12): a plugin that loads .p12 bundles from an untrusted source could be tricked into accepting a forged bundle.

Patches

The vulnerability is addressed by applying the following patch:

Impacted supported versions of Kong API Gateway Enterprise

Patch

3.15.0.0 - 3.15.0.2 3.15.0.3
3.14.0.0 - 3.14.0.11 3.14.0.12
3.13.0.0 - 3.13.0.8 3.13.0.9
3.12.0.0 - 3.12.0.9 3.12.0.10
3.10.0.0 - 3.10.0.16 3.10.0.17
3.4.0.0 - 3.4.3.28 3.4.3.29

Contact

If you have questions or need help, open a case with Kong Support or email support@konghq.com.

Help us make these docs great!

Kong Developer docs are open source. If you find these useful and want to make them better, contribute today!