Live › vulnerability › CVE-2026-41510
Go to dashboardCoraza, a Go web application firewall library, silently drops request arguments beyond SecArgumentsLimit, so ARGS-targeted rules never see them. An unauthenticated attacker can flood a request with arguments to hide a payload from WAF rules and also drive excess memory use and service degradation.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/corazawaf/coraza | go | all versions | – |
| github.com/corazawaf/coraza/v2 | go | all versions | – |
| github.com/corazawaf/coraza/v3 | go | >= 3.0.0, < 3.8.1 | 3.8.1 |
Check go.mod for github.com/corazawaf/coraza/v3 at a version >= 3.0.0 and < 3.8.1, e.g. go list -m github.com/corazawaf/coraza/v3
The sources do not give a command for checking whether the app is exposed to parameter flooding.
3.8.1 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. From 3.0.0 until 3.8.1, Coraza silently drops arguments after SecArgumentsLimit in internal/corazawaf/transaction.go, while internal/bodyprocessors/urlencoded.go writes ARGS_POST without enforcing the cap. The flaw is triggered when an unauthenticated attacker sends more arguments than SecArgumentsLimit or supplies bodies that expand beyond the configured argument and flattening budgets. An unauthenticated attacker can flood requests with arguments so excess values are silently omitted from ARGS, ARGS_GET, ARGS_NAMES, ARGS_GET_NAMES, ARGS_POST, or ARGS_PATH before security rules inspect them; affected urlencoded and JSON processing can also consume excessive memory. The omission can bypass WAF rules protecting the downstream application, and unbounded or amplified argument processing can cause memory consumption and service degradation. This issue is fixed in version 3.8.1.
This page as .md · .json · in your agent: get_signal("CVE-2026-41510")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.