Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-41510 high CVSS 7.2

Vulnerability in github.com/corazawaf/coraza/v3 (CVE-2026-41510)

Summary

Vulnerability in github.com/corazawaf/coraza/v3 (CVE-2026-41510). Risk of unauthorized operations or information disclosure. Exploitable via AddGetRequestArgument. Mitigation: upgrade to 3.8.1 or later.

Original description

The description as published by the source.

Root Cause

File: internal/corazawaf/transaction.go, lines 770–808 (since commit 2fd87b89, PR #812, 2023-06-14)

func (tx *Transaction) AddGetRequestArgument(key string, value string) {
    if tx.checkArgumentLimit(tx.variables.argsGet) {
        tx.debugLogger.Warn().Msg("skipping get request argument, over limit")
        return
    }
    tx.variables.argsGet.Add(key, value)
}

func (tx *Transaction) checkArgumentLimit(c *collections.NamedCollection) bool {
    return c.Len() >= tx.WAF.ArgumentLimit
}

AddGetRequestArgument, AddPostRequestArgument, and AddPathRequestArgument silently return once the per-collection argument count reaches WAF.ArgumentLimit (default 1000, see internal/corazawaf/waf.go:346). No error variable is set, no transaction flag is raised, and no rule can observe that a drop occurred.

Worse, ExtractGetArguments (transaction.go:761) iterates the map[string][]string returned by urlutil.ParseQuery:

func (tx *Transaction) ExtractGetArguments(uri string) {
    data := urlutil.ParseQuery(uri, '&')
    for k, vs := range data {        // Go map iteration order is randomized
        for _, v := range vs {
            tx.AddGetRequestArgument(k, v)
        }
    }
}

Because Go randomizes map iteration order, which of the caller-supplied arguments survive the limit is non-deterministic. An attacker can pad the URI with filler arguments; any one of them — including the malicious payload — may be the one silently di…

Source: GitHub Security Advisories (Global) 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-41510 has been found in github.com/corazawaf/coraza/v3.
Attackers can target a specific entry point like AddGetRequestArgument over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.2/10.
What to do: upgrade github.com/corazawaf/coraza/v3 to 3.8.1 or later.
If unsure, ask your IT team or search "github.com/corazawaf/coraza/v3 CVE-2026-41510" on the vendor's site.

CVE-2026-41510 (github.com/corazawaf/coraza/v3) — CWE-693 / CVSS v3 7.2
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: AddGetRequestArgument / AddPostRequestArgument / AddPathRequestArgument / return
Patched: 3.8.1 — 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-693) exists in github.com/corazawaf/coraza/v3. Attackers reach the vulnerable code path via AddGetRequestArgument without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/corazawaf/coraza/v3. Attack surface: AddGetRequestArgument / AddPostRequestArgument / AddPathRequestArgument / return.

🔥 Severity

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

🔧 How to fix

Update to 3.8.1.

🛡️ 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/corazawaf/coraza/v3' . 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/corazawaf/coraza/v3' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade github.com/corazawaf/coraza/v3 to 3.8.1

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

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

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

Affected packages

go github.com/corazawaf/coraza/v3
[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.8.1"}]}]

References

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