CVE-2026-61629

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 53% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (2)

Auto-updated Sep 21, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit

commit 0c988fc1277c (lucasdillmann/nginx-ignition)

Fix landed in lucasdillmann/nginx-ignition commit 0c988fc1277c — awaiting tagged release

https://github.com/lucasdillmann/nginx-ignition/commit/0c988fc1277c7d291725e8373313f8486fa1b31a
github Patch Available🟡 PoC Available

ParseAcceptLanguage `_` separator bypass enables ~75x CPU amplification via Accept-Language header in i18nMiddleware · Advisory · lucasdillmann/nginx-ignition · GitHub

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

Vendor Advisories for CVE-2026-61629(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/lucasdillmann/nginx-ignition—0.0.0-20260526022344-0c988fc1277c—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 9× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 23:38 UTCEG score recompute
  2. 2026-09-24 22:27 UTCEG score recompute
  3. 2026-09-24 18:00 UTCEG score recompute
  4. 2026-09-23 18:39 UTCEG score recompute
  5. 2026-09-23 17:54 UTCEPSS rescore
  6. 2026-09-23 01:26 UTCEG score recompute
  7. 2026-09-21 15:22 UTCEG score recompute
  8. 2026-09-21 14:25 UTCEG score recompute
  9. 2026-09-21 14:25 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/lucasdillmann/nginx-ignition

Frequently asked(5)

What is CVE-2026-61629?
CVE-2026-61629 is a high vulnerability published on September 21, 2026. 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…
When was CVE-2026-61629 disclosed?
CVE-2026-61629 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61629 actively exploited?
CVE-2026-61629 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.1% of all scored CVEs.
What is the CVSS score of CVE-2026-61629?
CVE-2026-61629 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-61629?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61629, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-61629

Explore →

Is Your Infrastructure Affected by CVE-2026-61629?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs