{"id":"CVE-2026-92441","kind":"vulnerability","aliases":["CVE-2026-92441"],"related":[],"title":"Kong Gateway: decoded line breaks in request path enable header injection","description":"Kong Gateway Enterprise and Kong AI Gateway include decoded CR/LF characters from the request path in the X-Forwarded-Prefix header on regex Routes, allowing HTTP header injection and request smuggling to the upstream.","summary":"Kong Gateway Enterprise and Kong AI Gateway copy decoded CR and LF characters from the request path into the X-Forwarded-Prefix header on regex Routes. An attacker can inject HTTP headers and smuggle requests to the upstream service.","severity":"high","cvss":7.8,"epss":null,"exploited":false,"exploited_at":null,"products":[{"name":"kong-gateway-enterprise","fixed":["3.16.0.2","3.15.0.7"],"affected":"unknown; affected ranges not published in the sources read","ecosystem":"vendor"}],"ecosystems":[],"tags":["api-gateway","infrastructure","kong","kong-ai-gateway"],"not_affected_if":["no-regex-routes"],"how_to_check":"- Run 'kong version' on each Kong Gateway Enterprise / Kong AI Gateway node; below 3.16.0.2 on 3.16.x or below 3.15.0.7 on 3.15.x is unpatched. Older branches: unknown, ask Kong.\n- Check for Routes with regex paths (paths starting with ~), in kong.yaml or via the Admin API /routes. The NVD description limits the issue to regex Routes.\n- Check whether the upstream reads X-Forwarded-Prefix. Kong's changelog names the header X-Forwarded-Path, so check both.","fix":"Kong Gateway Enterprise: upgrade to 3.16.0.2 (3.16 branch) or 3.15.0.7 (3.15 branch), both released 2026-11-10. Fixes for older branches: unknown, not listed in the changelog.","status":"open","published_at":"2026-11-10T22:21:14+00:00","first_seen_at":"2026-11-10T22:27:31+00:00","triaged_at":"2026-11-10T22:29:07+00:00","updated_at":"2026-11-10T22:36:57+00:00","category":"infrastructure","confidence":0.6,"triage":{"at":"2026-11-10T22:29:07Z","model":"claude-haiku-5-5","output":{"fix":"unknown","reach":"internet","title":"Kong Gateway: decoded line breaks in request path enable header injection","impact":"medium","summary":"Kong Gateway Enterprise and Kong AI Gateway copy decoded CR and LF characters from the request path into the X-Forwarded-Prefix header on regex Routes. An attacker can inject HTTP headers and smuggle requests to the upstream service.","audience":"businesses","category":"infrastructure","nicknames":[],"who_cares":["kong","api-gateway","kong-ai-gateway"],"confidence":0.6,"fix_status":"unknown","needs_auth":"unknown","worst_case":"Attacker injects headers and smuggles requests to upstream services.","analyst_note":"Get affected version ranges and fixed versions from the NVD entry and Kong's security advisory; confirm the regex-Route condition and whether authentication is required.","how_to_check":"- Check whether the Kong Gateway Enterprise or Kong AI Gateway version in use is listed as affected in the advisory: unknown\n- Check whether any Route in Kong uses a regex path, since the description says only regex Routes are affected: unknown\n- Check whether the gateway forwards or relies on the X-Forwarded-Prefix header: unknown","plain_action":"","product_name":"","needs_analyst":true,"not_affected_if":["no-regex-routes"],"who_is_affected":"Teams running Kong Gateway Enterprise or Kong AI Gateway with regex-based Routes are exposed, because the flaw is in how the path is copied into X-Forwarded-Prefix. Deployments that use only plain-prefix Routes are not described as affected. The sources do not give the affected version ranges.","user_interaction":"no","product_ecosystem":"","needs_special_setup":"yes","severity_if_unknown":"high"},"cost_usd":0.000765,"input_tokens":4536,"output_tokens":622,"severity_before":"high"},"analyst_status":"done","analyst_note":"Get affected version ranges and fixed versions from the NVD entry and Kong's security advisory; confirm the regex-Route condition and whether authentication is required.","search":"'-2026':13A,16A '-92441':14A,17A 'ai':29B,36B,76C 'allow':96C 'api':23B 'api-gateway':22B 'attack':59B 'break':5A 'charact':43B,81C 'copi':38B 'cr':40B 'cr/lf':80C 'cve':12A,15A 'decod':3A,39B,79C 'enabl':9A 'enterpris':33B,73C 'enterprise':21A 'forward':52B,90C 'gateway':2A,20A,24B,30B,32B,37B,72C,77C 'header':10A,54B,63B,92C,98C 'http':62B,97C 'includ':78C 'infrastructur':25B 'inject':11A,61B,99C 'kong':1A,19A,26B,28B,31B,35B,71C,75C 'kong-ai-gateway':27B 'kong-gateway-enterprise':18A 'lf':42B 'line':4A 'path':8A,47B,85C 'prefix':53B,91C 'regex':56B,94C 'request':7A,46B,66B,84C,101C 'rout':57B,95C 'servic':70B 'smuggl':65B,102C 'upstream':69B,105C 'x':51B,89C 'x-forwarded-prefix':50B,88C","nicknames":[],"mitigations":[],"who_affected":"Teams running Kong Gateway Enterprise or Kong AI Gateway with regex-based Routes are exposed, because the flaw is in how the path is copied into X-Forwarded-Prefix. Deployments that use only plain-prefix Routes are not described as affected. The sources do not give the affected version ranges.","tier":"B","verified":{"fix":{"at":"2026-11-10T22:36:57Z","by":"analyst","doc":"https://developer.konghq.com/gateway/changelog/","run_id":3010}},"analyst_revisit_at":null,"fix_status":"none","audience":"businesses","plain_action":null,"pkeys":["konggatewayenterprise"],"ptokens":["enterprise","gateway","kong"],"labels":["apigateway","high","infrastructure","kong","kongaigateway"],"campaign_type":null,"search_a":"'-2026':13A,16A '-92441':14A,17A 'break':5A 'cve':12A,15A 'decod':3A 'enabl':9A 'enterprise':21A 'gateway':2A,20A 'header':10A 'inject':11A 'kong':1A,19A 'kong-gateway-enterprise':18A 'line':4A 'path':8A 'request':7A","search_b":"'ai':29B,36B 'api':23B 'api-gateway':22B 'attack':59B 'charact':43B 'copi':38B 'cr':40B 'decod':39B 'enterpris':33B 'forward':52B 'gateway':24B,30B,32B,37B 'header':54B,63B 'http':62B 'infrastructur':25B 'inject':61B 'kong':26B,28B,31B,35B 'kong-ai-gateway':27B 'lf':42B 'path':47B 'prefix':53B 'regex':56B 'request':46B,66B 'rout':57B 'servic':70B 'smuggl':65B 'upstream':69B 'x':51B 'x-forwarded-prefix':50B","search_c":"'ai':76C 'allow':96C 'charact':81C 'cr/lf':80C 'decod':79C 'enterpris':73C 'forward':90C 'gateway':72C,77C 'header':92C,98C 'http':97C 'includ':78C 'inject':99C 'kong':71C,75C 'path':85C 'prefix':91C 'regex':94C 'request':84C,101C 'rout':95C 'smuggl':102C 'upstream':105C 'x':89C 'x-forwarded-prefix':88C","cause_entry":null,"cause_path":null,"disclosures_checked_at":null,"first_public_at":"2026-11-10T22:21:14+00:00","kev":null,"cvss_vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cvss_by":"02762ae7-200e-4b20-9b2b-a77d5b8fc4cb","poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-92441","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-92441","severity":null,"published_at":"2026-11-10T22:21:14+00:00","modified_at":"2026-11-10T22:21:14+00:00","first_seen_at":"2026-11-10T22:27:31+00:00","fetched_at":"2026-11-10T22:27:31+00:00","note":null},{"source":"analyst","external_id":"CVE-2026-92441:3010","url":"https://developer.konghq.com/gateway/changelog/","severity":null,"published_at":"2026-11-10T22:36:57+00:00","modified_at":"2026-11-10T22:36:57+00:00","first_seen_at":"2026-11-10T22:36:57+00:00","fetched_at":"2026-11-10T22:36:57+00:00","note":"Kong changelog (vendor) lists the fix in 3.16.0.2 and 3.15.0.7 (2026-11-10). It says the header is X-Forwarded-Path, not X-Forwarded-Prefix as in the NVD description. Affected ranges, authentication requirement and a standalone advisory were not found; the Kong PSA page did not render. Fix verified only for those two branches.","cites":["https://developer.konghq.com/gateway/changelog/"]}],"documents":[{"id":119284,"url":"https://developer.konghq.com/gateway/changelog/","title":"Kong Gateway changelog (3.16.0.2)","kind":"release","source":"analyst","publisher":null,"text":null,"published_at":null,"relation":"fix","confidence":null,"note":null}],"disclosures":[],"exploit_sources":[],"notice":"Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai"}