Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61629 high CVSS 7.5

Vulnerability in github.com/lucasdillmann/nginx-ignition (CVE-2026-61629)

Summary

Vulnerability in github.com/lucasdillmann/nginx-ignition (CVE-2026-61629). Risk of unauthorized operations or information disclosure. Exploitable via main. Mitigation: upgrade to 0.0.0-20260526022344-0c988fc1277c or later.

Original description

The description as published by the source.

Summary

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.

Affected versions

dillmann.com.br/nginx-ignition v2.40.0 and (per code inspection of main) earlier 2.x versions whose api/common/server/i18n.go middleware routes the Accept-Language header through language.ParseAcceptLanguage without imposing its own size or character filter. Verified on:

  • the official dillmann/nginx-ignition:latest Docker image at v2.40.0 (E2E below)
  • main at commit faef4c99442b329cfa4ee8879bdba41c22866a18 by reading api/common/server/i18n.go (the middleware is unchanged)

Privilege required

Unauthenticated. The middleware is registered on the global gin router that serves bo…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61629 has been found in github.com/lucasdillmann/nginx-ignition.
Attackers can target a specific entry point like main over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/lucasdillmann/nginx-ignition to 0.0.0-20260526022344-0c988fc1277c or later.
If unsure, ask your IT team or search "github.com/lucasdillmann/nginx-ignition CVE-2026-61629" on the vendor's site.

CVE-2026-61629 (github.com/lucasdillmann/nginx-ignition) — CWE-770 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: main / language.ParseAcceptLanguage / faef4c99442b329cfa4ee8879bdba41c22866a18 / MaxHeaderBytes
Patched: 0.0.0-20260526022344-0c988fc1277c — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-770) exists in github.com/lucasdillmann/nginx-ignition. Attackers reach the vulnerable code path via main without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/lucasdillmann/nginx-ignition. Attack surface: main / language.ParseAcceptLanguage / faef4c99442b329cfa4ee8879bdba41c22866a18 / MaxHeaderBytes.

🔥 Severity

Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.0.0-20260526022344-0c988fc1277c.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/lucasdillmann/nginx-ignition' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/lucasdillmann/nginx-ignition' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/lucasdillmann/nginx-ignition を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/lucasdillmann/nginx-ignition to 0.0.0-20260526022344-0c988fc1277c

    ステージング環境で 0.0.0-20260526022344-0c988fc1277c に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/lucasdillmann/nginx-ignition
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.0-20260526022344-0c988fc1277c"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details