Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-107825 medium CVSS 4.0

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

Summary

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

Original description

The description as published by the source.

Root Cause

File: internal/corazawaf/transaction.go, lines 834–866.

parsedURL, err := url.ParseRequestURI(uri)
query := ""
if err != nil {
    tx.variables.urlencodedError.Set(err.Error())
    path = uri
    tx.variables.requestURI.Set(uri)
    /*
        tx.Variables.VARIABLE_URI_PARSE_ERROR.Set("1")
        posRawQuery := strings.Index(uri, "?")
        if posRawQuery != -1 {
            tx.ExtractArguments("GET", uri[posRawQuery+1:])
            path = uri[:posRawQuery]
            query = uri[posRawQuery+1:]
        } else {
            path = uri
        }
        tx.Variables.RequestUri.Set(uri)
    */
} else {
    tx.ExtractGetArguments(parsedURL.RawQuery)   // only path that populates ARGS_GET
    tx.variables.requestURI.Set(parsedURL.String())
    path = parsedURL.Path
    query = parsedURL.RawQuery
}
...
tx.variables.queryString.Set(query)

When url.ParseRequestURI(uri) returns an error — which Go's stdlib does for any URI containing raw control bytes (\x00, \n, \r, \t, other 0x00–0x1F, 0x7F) — the error branch silently produces an empty QUERY_STRING and an empty ARGS_GET collection. The fallback logic that should split on ? and populate the GET arguments from the raw tail is already present in the source as a commented-out block, referencing a VARIABLE_URI_PARSE_ERROR variable that was never wired up.

Consequences on the error branch:

  • ARGS_GET / ARGS_GET_NAMES / ARGS (union) are empty — ExtractGetArguments is ne…

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

CVE-2026-107825 (github.com/corazawaf/coraza/v3) — CWE-20 / CVSS v3 4.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: QUERY_STRING / ARGS_GET / VARIABLE_URI_PARSE_ERROR / ARGS_GET_NAMES
Patched: 3.8.0 — 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-20) exists in github.com/corazawaf/coraza/v3. Attackers reach the vulnerable code path via QUERY_STRING without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/corazawaf/coraza/v3. Attack surface: QUERY_STRING / ARGS_GET / VARIABLE_URI_PARSE_ERROR / ARGS_GET_NAMES.

🔥 Severity

Severity: Medium (CVSS 4.0/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.8.0.

🛡️ 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.0

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

  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.0"}]}]

References

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