Owasp vulnerabilities
We track 10 vulnerabilities in Owasp products across 6 products. 10 are rated high or critical, and none are known to be exploited. The most recent was published on April 15, 2026.
Latest Owasp vulnerabilities
- 8.8 High severity
BLT: Improper Control of Generation of Code
OWASP BLT is a QA testing and vulnerability disclosure platform that encompasses websites, apps, git repositories, and more. Versions prior to 2.1.1 contain an RCE vulnerability in the .github/workflows/regenerate-migrations.yml workflow. The workflow uses the
- 7.5 High severity
coreruleset: Improper Handling of Case Sensitivity
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, .p
- 9.8 Critical severity
Coreruleset: Access of Resource Using Incompatible Type
coreruleset (aka OWASP ModSecurity Core Rule Set) through 3.3.4 does not detect multiple Content-Type request headers on some platforms. This might allow attackers to bypass a WAF with a crafted payload, aka "Content-Type confusion" between the WAF and the bac
- 7.5 High severity
Modsecurity: Uncontrolled Resource Consumption
Trustwave ModSecurity 3.0.5 through 3.0.8 before 3.0.9 allows a denial of service (worker crash and unresponsiveness) because some inputs cause a segfault in the Transaction class for some configurations.
- 7.5 High severity
Modsecurity: Interpretation Conflict
In ModSecurity before 2.9.6 and 3.x before 3.0.8, HTTP multipart requests were incorrectly parsed and could bypass the Web Application Firewall. NOTE: this is related to CVE-2022-39956 but can be considered independent changes to the ModSecurity (C language) c
- 7.5 High severity
ModSecurity Core Rule Set: Improper Encoding or Escaping of Output
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 range. A restricted resource, access to whi
- 7.5 High severity
ModSecurity Core Rule Set: Improper Encoding or Escaping of Output
The OWASP ModSecurity Core Rule Set (CRS) is affected by a response body bypass. A client can issue an HTTP Accept header field containing an optional "charset" parameter in order to receive the response in an encoded form. Depending on the "charset", this res
- 9.8 Critical severity
ModSecurity Core Rule Set: Improper Encoding or Escaping of Output
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 Content-Transfer-Encoding multipart MIME header
- 9.8 Critical severity
ModSecurity Core Rule Set: Incorrect Authorization
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. A vulnerable back-end can potentially be exploited by declar
- 9.8 Critical severity
org.owasp.esapi:esapi: Improper Limitation of a Pathname to a Restricted Directory
ESAPI (The OWASP Enterprise Security API) is a free, open source, web application security control library. Prior to version 2.3.0.0, the default implementation of `Validator.getValidDirectoryPath(String, String, File, boolean)` may incorrectly treat the teste