Most recent entries from all

fkie_cve-2026-104269

ModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. From 3.0.0 until 3.0.17, ModSecurity's multipart parser does not apply the RFC 2231 filename* parameter precedence used by common Go, Python, Node.js, and Java application parsers. A Content-Disposition header can provide a benign filename parameter for ModSecurity and a different encoded filename* value that the backend prefers, causing MULTIPART_FILENAME rules and the application to make security decisions on different names. Applications that use the backend-selected name for storage, extension checks, or content-type inference can therefore receive a filename that bypassed WAF inspection. PHP's native multipart parser is not affected by this discrepancy. This issue is fixed in version 3.0.17.

UBUNTU-CVE-2026-104269

Affected: Ubuntu:Pro:14.04:LTS: modsecurity-apache, Ubuntu:Pro:16.04:LTS: modsecurity-apache, Ubuntu:Pro:18.04:LTS: modsecurity-apache, Ubuntu:20.04:LTS: modsecurity, Ubuntu:Pro:20.04:LTS: modsecurity-apache, Ubuntu:22.04:LTS: modsecurity, Ubuntu:Pro:22.04:LTS: modsecurity-apache, Ubuntu:24.04:LTS: modsecurity, Ubuntu:Pro:24.04:LTS: modsecurity-apache, Ubuntu:26.10: modsecurity and 3 more

[GHSA-5pww-8rfg-9crf: RFC 2231 filename* parameter bypasses multipart filename rules]

WID-SEC-W-2026-3666 — OWASP ModSecurity: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in OWASP ModSecurity ausnutzen, um Sicherheitsvorkehrungen zu umgehen, um Informationen offenzulegen und um einen Denial of Service Angriff durchzuführen.