Categories
CVE-2026-107835 medium CVSS 4.0

Vulnerability in OWASP Coraza WAF (CVE-2026-107835)

Summary

Vulnerability in OWASP Coraza WAF (CVE-2026-107835). Risk of unauthorized operations or information disclosure. Exploitable via Cookie header.

Original description

The description as published by the source.

OWASP Coraza WAF is a golang modsecurity compatible web application firewall library. Prior to 3.8.1, internal/cookies.ParseCookies in internal/cookies/cookies.go handles boundary ASCII control characters and control-only or empty cookie names differently from several backend cookie parsers. An unauthenticated attacker can craft a Cookie header so Coraza indexes or drops a cookie under a different name or value from the backend application, causing rules targeting REQUEST_COOKIES or REQUEST_COOKIES_NAMES to miss application-visible attacker data. Exploitation depends on the backend parser and affected rule scope, and interior control characters with inconsistent backend behavior are outside this advisory's remediation. This issue is fixed in version 3.8.1.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-107835 has been found in OWASP Coraza WAF.
Attackers can target a specific entry point like Cookie header over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OWASP Coraza WAF CVE-2026-107835" on the vendor's site.

CVE-2026-107835 (OWASP Coraza WAF) — CWE-436 / CVSS v3 4.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Cookie header
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-436) exists in OWASP Coraza WAF. Attackers reach the vulnerable code path via Cookie header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of OWASP Coraza WAF. Attack surface: Cookie header.

🔥 Severity

Severity: Medium (CVSS 4.0/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで OWASP Coraza WAF を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details