Coraza: ProcessURI silently drops QUERY_STRING and ARGS_GET on URI parse failure — defense-in-depth bypass for non-net/http integrations

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.0 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N

EPSS

• CVE-2026-107825: 0.32% estimated exploitation activity in the next 30 days; percentile 25.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Root Cause File: internal/corazawaf/transaction.go, lines 834–866. 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 QUERYSTRING and an empty ARGSGET 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 VARIABLEURIPARSEERROR variable that was never wired up. Consequences on the error branch: - ARGSGET / ARGSGETNAMES / ARGS (union) are empty — ExtractGetArguments is never called. - QUERYSTRING is empty (initial query := "" at line 835 persists through to queryString.Set(query) at line 866). - REQUESTFILENAME / REQUESTBASENAME contain the entire URI including any ?… query suffix (because path = uri at line 838 bypasses the parse, and the subsequent strings.LastIndexAny(path, "/\\") runs over the raw URI). -…

Published by the source

8 Oct 2026, 17:46 UTC

Last modified by the source

19 Oct 2026, 21:41 UTC

Source last checked

26 Oct 2026, 15:32 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x26q-wvhg-fh4m

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6699

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-x26q-wvhg-fh4m

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107825

Advisory: Coraza: ProcessURI silently drops QUERY_STRING and ARGS_GET on URI parse failure — defense-in-depth bypass for non-net/http integrations
IDs: CVE-2026-107825, GHSA-x26q-wvhg-fh4m
Record: https://patchnext.com/advisories/cve-2026-107825 (revision 3, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/corazawaf/coraza/v3 3.8.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/corazawaf/coraza/v3: affected >= 3.0.0, < 3.8.0; fixed in 3.8.0
- Go github.com/corazawaf/coraza: affected every version
- Go github.com/corazawaf/coraza/v2: affected every version

## Suggested inspection (read-only)
- Go github.com/corazawaf/coraza/v3: check the installed version with your package manager.
- Go github.com/corazawaf/coraza: check the installed version with your package manager.
- Go github.com/corazawaf/coraza/v2: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/corazawaf/coraza/v3, github.com/corazawaf/coraza, github.com/corazawaf/coraza/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6699 (OSV record GO-2026-6699 lists affected ranges: Go github.com/corazawaf/coraza >=0; Go github.com/corazawaf/coraza/v2 >=0; Go github.com/corazawaf/coraza/v3 >=3.0.0 <3.8.0 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-x26q-wvhg-fh4m (OSV record GHSA-x26q-wvhg-fh4m lists affected ranges: Go github.com/corazawaf/coraza/v3 >=3.0.0 <3.8.0 (fixed))
- Verified: https://github.com/advisories/GHSA-x26q-wvhg-fh4m (GitHub-reviewed advisory GHSA-x26q-wvhg-fh4m lists affected ranges: Go github.com/corazawaf/coraza/v3 >=3.0.0 <3.8.0)

Commands are suggestions: review each one before running it.