cve.bz

CVE-2026-107825 corazawaf coraza: Interpretation Conflict

4.0 mediumEPSS 0.3%Fix available

Medium (4.0) in corazawaf coraza. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/corazawaf/coraza/v3 3.8.0.

On this page
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.

Severity

CVSS 3.1

4.0 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 26th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-436 Interpretation Conflict
OWASP Top 10
A05:2025 Injection, A06:2025 Insecure Design
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • github.com/corazawaf/coraza/v3 (Go): fixed in 3.8.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-107825 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107825?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107825?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107825 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
corazawaf coraza>= 3.0.0, < 3.8.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-x26q-wvhg-fh4mGogithub.com/corazawaf/coraza/v3>=3.0.0 <3.8.03.8.0
GO-2026-6699Gogithub.com/corazawaf/corazaall versionsno fix published
GO-2026-6699Gogithub.com/corazawaf/coraza/v2all versionsno fix published
GO-2026-6699Gogithub.com/corazawaf/coraza/v3>=3.0.0 <3.8.03.8.0

Attack patterns (CAPEC)

  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON