Skip to main content

Threat Intelligence Database

Comprehensive database of the latest cyber threats affecting organizations worldwide. Filter and search to find specific threat intelligence relevant to your organization.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Package: pkg:github/corazawaf/coraza

Threat Intelligence

Click on any threat for detailed analysis and mitigation recommendations

CVE-2026-107834 is a medium severity vulnerability in OWASP Coraza WAF versions 3.0.0 through 3.7.x. It involves uncontrolled resource consumption due to the handling of multipart file uploads, where temporary file descriptors remain open until the entire request completes. An unauthenticated attacker can exploit this by sending many minimal file parts in a multipart request, exhausting the process file descriptor table and causing failures in creating temporary files, blocking legitimate uploads, and preventing the process from opening files or sockets. This issue is fixed in version 3.8.0.

Join the discussion

OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. From 3.0.0 until 3.8.0, ProcessResponse in internal/bodyprocessors/json.go passes the ignoreJSONRecursionLimit value of -1 to readJSON, while the recursive guard only stops at zero. A network attacker who can cause an application protected by Coraza to return deeply nested JSON can make response-body processing perform quadratic work, consuming one CPU core for seconds per response within the default ResponseBodyLimit. Request JSON processing is not affected by this specific path because it uses the configured request recursion limit, and exploitation requires response-body inspection to be enabled. This issue is fixed in version 3.8.0.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Package: pkg:github/corazawaf/coraza
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses