Owasp Modsecurity Core Rule Set vulnerabilitiesRanked by how likely they are to be used.
Owasp Modsecurity Core Rule Set is made by Owasp. We track 8 published vulnerabilities in it, across 16 versions. None of them is on the list of flaws known to be exploited today. If you run Owasp Modsecurity Core Rule Set, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Owasp Modsecurity Core Rule Set vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Owasp Modsecurity Core Rule Set's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Owasp Modsecurity Core Rule Set flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 2.7%CVE-2021-35368Critical
OWASP ModSecurity Core Rule Set 3.1.x before 3.1.2, 3.2.x before 3.2.1, and 3.3.x before 3.3.2 is affected by a Request Body Bypass via a trailing pathname.
- 1.7%CVE-2018-16384High
A SQL injection bypass (aka PL1 bypass) exists in OWASP ModSecurity Core Rule Set (owasp-modsecurity-crs) through v3.1.0-rc3 via {`a`b} where a is a special function name (such as "if") and b is the SQL statement to...
- 1.6%CVE-2026-33691Medium
The OWASP core rule set (CRS) is a set of generic attack detection rules for use with compatible web application firewalls.
- 1.4%CVE-2022-39955High
The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass by submitting a specially crafted HTTP Content-Type header field that indicates multiple character encoding schemes.
- 1.3%CVE-2020-22669Critical
Modsecurity owasp-modsecurity-crs 3.2.0 (Paranoia level at PL1) has a SQL injection bypass vulnerability.
- 1.2%CVE-2022-39958High
The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass to sequentially exfiltrate small and undetectable sections of data by repeatedly submitting an HTTP Range header field with a small byte...
- 1.2%CVE-2022-39956High
The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass for HTTP multipart requests by submitting a payload that uses a character encoding scheme via the Content-Type or the deprecated...
- 1.0%CVE-2022-39957High
The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass.
Running Owasp Modsecurity Core Rule Set? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
OWASP ModSecurity Core Rule Set 3.1.x before 3.1.2, 3.2.x before 3.2.1, and 3.3.x before 3.3.2 is affected by a Request Body Bypass via a trailing pathname.
- Matched to
- Owasp Modsecurity Core Rule Set on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 8 published vulnerabilities listed under the name Owasp Modsecurity Core Rule Set, across 16 versions.
None of Owasp Modsecurity Core Rule Set's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Owasp Modsecurity Core Rule Set. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.