cve.bz

CVE-2026-33691 owasp owasp modsecurity core rule set: Improper Handling of Case Sensitivity

7.5 highEPSS 3.9%Fix available

High (7.5) in owasp owasp modsecurity core rule set. EPSS 3.9% estimated probability of exploitation activity in the next 30 days.

On this page
The OWASP core rule set (CRS) is a set of generic attack detection rules for use with compatible web application firewalls. Prior to versions 3.3.9 and 4.25.0, a bypass was identified in OWASP CRS that allows uploading files with dangerous extensions (.php, .phar, .jsp, .jspx) by inserting whitespace padding in the filename (e.g. photo. php or shell.jsp ). The affected rules do not normalize whitespace before evaluating the file extension regex, so the dot-extension check fails to match. This issue has been patched in versions 3.3.9 and 4.25.0.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
3.9% (unchanged from 3.8% a week ago; 1.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 91st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-04-02. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-178 Improper Handling of Case Sensitivity
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-33691 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-33691?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-33691?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-33691 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 NVD's CPE matches.

ProductAffected
owasp:owasp_modsecurity_core_rule_setbefore 3.3.9
owasp:owasp_modsecurity_core_rule_setfrom 4.0.0 before 4.25.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12modsecurity-crs3.3.4-1+deb12u3DEBIAN-CVE-2026-33691
Debian13modsecurity-crs3.3.7-1+deb13u2DEBIAN-CVE-2026-33691
Debian14modsecurity-crs3.3.9-1DEBIAN-CVE-2026-33691
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 5 moremodsecurity-crsno fix listedUBUNTU-CVE-2026-33691
openSUSETumbleweedowasp-modsecurity-crs4.29.0-1.1openSUSE-SU-2026:11632-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

References

Check your stackJSON