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

> Attackers can bypass WAF rules by sending malformed URIs in non-standard integrations, causing query parameters to be ignored during inspection.

- **Severity:** Medium 4.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-x26q-wvhg-fh4m, GO-2026-6699

## What is CVE-2026-107825?

CVE-2026-107825 is a medium-severity vulnerability in corazawaf coraza, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. From 3.0.0 until 3.8.0, ProcessURI in internal/corazawaf/transaction.go handles a url.ParseRequestURI failure by retaining the raw URI but leaving QUERY_STRING, ARGS_GET, ARGS_GET_NAMES, and the GET-derived portion of ARGS empty. An unauthenticated attacker can place control bytes in a URI passed directly by integrations such as coraza-spoa, coraza-proxy-wasm, custom FFI hosts, or WASM hosts, causing Coraza to omit query parameters that the downstream integration may still process and allowing rules targeting those variables to be bypassed. The bundled coraza/v3/http integration is not affected because Go net/http rejects such malformed request targets before calling Coraza. This issue is fixed in version 3.8.0.

Weakness: CWE-436 (Interpretation Conflict), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-107825?

5 open source packages ship an affected version, including github.com/corazawaf/coraza/v3, github.com/corazawaf/coraza and github.com/corazawaf/coraza/v2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/corazawaf/coraza/v3` | Go | From 3.0.0 | 3.8.0 |
| `github.com/corazawaf/coraza/v3` | Go | From 3.0.0 | 3.8.0 |
| `github.com/corazawaf/coraza/v3` | Go | From 3.0.0 | 3.8.0 |
| `github.com/corazawaf/coraza` | Go | All versions | None |
| `github.com/corazawaf/coraza/v2` | Go | All versions | None |

## How do I fix CVE-2026-107825?

Upgrade github.com/corazawaf/coraza/v3 to 3.8.0 or later.

## Is CVE-2026-107825 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107825 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107825 and fix it if it is affected.

What it is: CVE-2026-107825 is a medium-severity vulnerability in corazawaf coraza, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107825 exists.

Affected packages and fixed versions:
- github.com/corazawaf/coraza/v3 (Go): affected from 3.0.0; fixed in 3.8.0
- github.com/corazawaf/coraza/v3 (Go): affected from 3.0.0; fixed in 3.8.0
- github.com/corazawaf/coraza/v3 (Go): affected from 3.0.0; fixed in 3.8.0
- github.com/corazawaf/coraza (Go): affected all versions; no fix listed
- github.com/corazawaf/coraza/v2 (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107825/ (Markdown: https://insights.sbomify.com/CVE-2026-107825/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107825
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107825
- OSV: https://osv.dev/vulnerability/CVE-2026-107825

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107825/
Summaries are generated and may contain mistakes; the official description above is the record.