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.