Security Advisory: CVE-2026-42934

Uses: Kong Gateway
Severity
Medium
Published
2026-06-05
Fixed versions
  • 3.14.0.4
  • 3.13.0.5
  • 3.12.0.7
  • 3.11.0.12
  • 3.10.0.12
  • 3.4.3.27
Affected versions
  • 3.14.0.0 to 3.14.0.3
  • 3.13.0.0 to 3.13.0.4
  • 3.12.0.0 to 3.12.0.6
  • 3.11.0.0 to 3.11.0.11
  • 3.10.0.0 to 3.10.0.11
  • 3.4.0.0 to 3.4.3.26

CVE

Description

Severity

CVE-2026-42934 NGINX ngx_http_charset_module vulnerability when charset conversion is combined with proxying and disabled response buffering Medium

CVE-2026-42934

CVE-2026-42934 affects the NGINX ngx_http_charset_module. The vulnerable condition requires charset conversion to be configured together with proxying where response buffering is disabled.

Kong doesn’t configure the required charset conversion pattern by default, such as:

charset windows-1251;
source_charset utf-8;
include win-utf;

Disabling response buffering alone isn’t sufficient to trigger this CVE. Kong supports disabling response buffering at the Route level, but without the problematic NGINX charset conversion configuration, the vulnerability condition isn’t met.

Users of custom NGINX directives or templates may have exposure, however.

Am I affected?

Check your custom NGINX configuration, including nginx.conf and nginx-kong.conf.

Customers using custom NGINX directives or templates should check whether charset, source_charset, or charset_map are configured together with proxy_pass and disabled proxy buffering. Review all of these conditions together against the upstream CVE trigger conditions.

Patches

The vulnerability is addressed by applying the patch appropriate for your version:

Impacted supported versions of Kong Gateway Enterprise

Patch

3.14.0.0 - 3.14.0.3 3.14.0.4
3.13.0.0 - 3.13.0.4 3.13.0.5
3.12.0.0 - 3.12.0.6 3.12.0.7
3.11.0.0 - 3.11.0.11 3.11.0.12
3.10.0.0 - 3.10.0.11 3.10.0.12
3.4.0.0 - 3.4.3.26 3.4.3.27

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!