{"id":"CVE-2022-39956","aliases":["DEBIAN-CVE-2022-39956","DLA-3293-1","DLA-4265-1","EUVD-2022-42400","GHSA-5xc6-pmr2-qj78","MGASA-2024-0070","OESA-2022-1964","OESA-2025-1559","OESA-2025-1560","OESA-2025-1561","UBUNTU-CVE-2022-39956"],"status":"published","title":"Partial rule set bypass in OWASP ModSecurity Core Rule Set  for HTTP multipart requests using  character encoding in the Content-Type or Content-Transfer-Encoding header","description":"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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).","severity":{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.01212,"percentile":0.68894,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-116","CWE-863"],"published":"2022-09-20T00:00:00Z","modified":"2026-11-03T08:02:54Z","fixes":[{"ecosystem":"Debian:12","package":"modsecurity-crs","fixed_in":["3.3.4-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"modsecurity-crs","fixed_in":["3.3.4-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"modsecurity-crs","fixed_in":["3.3.4-1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.4-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.4-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.4-1"}]}]},{"source":"osv","ecosystem":"Debian:10","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.3-0+deb10u3"}]}],"versions":["3.1.0-1","3.1.0-1+deb10u1","3.1.0-1+deb10u2","3.1.1-1","3.2.0-1"],"bundled":7},{"source":"osv","ecosystem":"Debian:11","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.4-1~deb11u1"}]}],"versions":["3.3.0-1","3.3.0-1+deb11u1","3.3.2-1"],"bundled":5},{"source":"osv","ecosystem":"Mageia:9","package":"apache-mod_security-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.3.5-1.mga9"}]}],"bundled":7},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"mod_security_crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.2-1.oe1"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP3","package":"mod_security_crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.2-1.oe1"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:22.03-LTS","package":"mod_security_crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.2.2-1.oe2203"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP4","package":"mod_security","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.9-1.oe2003sp4"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP3","package":"mod_security","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.9-1.oe2203sp3"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:22.03-LTS-SP4","package":"mod_security","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.9-1.oe2203sp4"}]}],"bundled":2},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.2.9-1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.0.0-3","3.0.2-1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.1.1-1","3.2.0-1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.3.0-1","3.3.2-1"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.3.5-1","3.3.5-2"]},{"source":"osv","ecosystem":"Ubuntu:25.10","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.3.7-1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.3.8-1","3.3.9-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"modsecurity-crs","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["3.3.7-1","3.3.8-1"]}],"products":[{"vendor":"debian","product":"debian_linux"},{"vendor":"fedoraproject","product":"fedora"},{"vendor":"owasp","product":"modsecurity core rule set"},{"vendor":"owasp","product":"owasp_modsecurity_core_rule_set"}],"references":[{"url":"https://coreruleset.org/20220919/crs-version-3-3-3-and-3-2-2-covering-several-cves/","tags":["x_transferred","Patch","Vendor Advisory","web","report"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PD56EAYNGB6E6QQH62LAYCONOP6OH5DZ/","tags":["vendor-advisory","x_transferred","advisory"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YPQ6CCMX3MU4A7MTCGQJA7VMJW3IQDXV/","tags":["vendor-advisory","x_transferred","advisory"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HL2L2GF7GOCWPMJZDUE5OXDSXHGG3XUJ/","tags":["vendor-advisory","x_transferred","advisory"]},{"url":"https://lists.debian.org/debian-lts-announce/2023/01/msg00033.html","tags":["mailing-list","x_transferred","Mailing List","Third Party Advisory","article"]},{"url":"https://security.gentoo.org/glsa/202305-25","tags":["vendor-advisory","x_transferred","advisory"]},{"url":"https://lists.debian.org/debian-lts-announce/2025/08/msg00004.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-39956","tags":["advisory"]},{"url":"https://coreruleset.org/20220919/crs-version-3-3-3-and-3-2-2-covering-several-cves"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/HL2L2GF7GOCWPMJZDUE5OXDSXHGG3XUJ"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PD56EAYNGB6E6QQH62LAYCONOP6OH5DZ"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/YPQ6CCMX3MU4A7MTCGQJA7VMJW3IQDXV"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/HL2L2GF7GOCWPMJZDUE5OXDSXHGG3XUJ"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PD56EAYNGB6E6QQH62LAYCONOP6OH5DZ"},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YPQ6CCMX3MU4A7MTCGQJA7VMJW3IQDXV"},{"url":"https://github.com/advisories/GHSA-5xc6-pmr2-qj78"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/39xxx/CVE-2022-39956.json","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2022-39956","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2024-0070.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=30977","tags":["report"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/C4Q7DCCE37GT5ZBJOWP4NGUD4L3FAMDB/","tags":["web"]},{"url":"https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/thread/6MS5GMNYHFFIBWLJW7N3XAD24SLF3PFZ/","tags":["web"]},{"url":"https://coreruleset.org/20210630/cve-2021-35368-crs-request-body-bypass/","tags":["web"]},{"url":"https://www.debian.org/lts/security/2023/dla-3293","tags":["web"]},{"url":"https://www.openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2022-1964","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-39955","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1559","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-47947","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1560","tags":["advisory"]},{"url":"https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2025-1561","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-39956","tags":["report"]},{"url":"https://bugs.debian.org/1020303","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-39956","tags":["report"]}],"sources":{"cve":[{"id":"CVE-2022-39956","title":"Partial rule set bypass in OWASP ModSecurity Core Rule Set  for HTTP multipart requests using  character encoding in the Content-Type or Content-Transfer-Encoding header","description":"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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).","status":"published","published":"2022-09-20T00:00:00Z","modified":"2025-11-03T19:27:30.25Z","cvss":[{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"high","assessor":"cna"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T14:34:39.559326Z"}],"euvd":[{"id":"EUVD-2022-42400","description":"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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).","status":"published","published":"2022-09-20T00:00:00Z","modified":"2025-11-03T19:27:30Z","cvss":[{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"high"}],"updated_at":"2026-11-02T19:49:34.152725Z"}],"ghsa":[{"id":"GHSA-5xc6-pmr2-qj78","title":"The OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule set bypass for HTTP...","description":"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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).","status":"published","published":"2022-09-21T00:00:52Z","modified":"2025-11-03T21:31:46Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"cwes":["CWE-116","CWE-863"],"updated_at":"2026-11-02T15:04:19.274788Z"}],"nvd":[{"id":"CVE-2022-39956","description":"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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).","status":"published","published":"2022-09-20T07:15:12.293Z","modified":"2026-06-17T04:58:34.957Z","cvss":[{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"high","assessor":"secondary"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical","assessor":"primary"}],"cwes":["CWE-863","CWE-116"],"updated_at":"2026-11-02T14:07:28.118799Z"}],"osv":[{"id":"CVE-2022-39956","title":"Partial rule set bypass in OWASP ModSecurity Core Rule Set  for HTTP multipart requests using  character encoding in the Content-Type or Content-Transfer-Encoding header","description":"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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).","status":"published","published":"2022-09-20T00:00:00Z","modified":"2026-10-28T02:30:44.31163343Z","cvss":[{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"high"}],"cwes":["CWE-863"],"updated_at":"2026-11-02T15:44:26.860704Z"},{"id":"DEBIAN-CVE-2022-39956","description":"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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).","status":"published","published":"2022-09-20T07:15:12.293Z","modified":"2026-11-03T08:02:54.841643913Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-03T08:24:39.643572Z"},{"id":"OESA-2022-1964","title":"mod_security_crs security update","description":"The base rules are provided for mod_security by this package.\r\n\r\nSecurity Fix(es):\r\n\r\nThe 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 declaring multiple Content-Type \u0026quot;charset\u0026quot; names and therefore bypassing the configurable CRS Content-Type header \u0026quot;charset\u0026quot; allow list. An encoded payload can bypass CRS detection this way and may then be decoded by the backend. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised to upgrade to 3.2.2 and 3.3.3 respectively.(CVE-2022-39955)\n\nThe 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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).(CVE-2022-39956)","status":"published","published":"2022-09-27T11:05:16Z","modified":"2026-08-18T01:17:18.659666938Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:39.528805Z"},{"id":"OESA-2025-1559","title":"mod_security security update","description":"This software is also called Modsec,it is an open-source web application firewall. It is designed for Apache HTTP Server.ModSecurity is commonly deployed to provide protections against generic classed of vulnerabilities.The install of this package is easy and you can read the README.TXT for more information.\r\n\r\nSecurity Fix(es):\n\nThe 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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).(CVE-2022-39956)\n\nModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. Versions up to and including 2.9.8 are vulnerable to denial of service in one special case (in stable released versions): when the payload\u0026apos;s content type is `application/json`, and there is at least one rule which does a `sanitiseMatchedBytes` action. A patch is available at pull request 3389 and expected to be part of version 2.9.9. No known workarounds are available.(CVE-2025-47947)","status":"published","published":"2025-05-30T11:08:39Z","modified":"2026-08-18T01:17:59.034211148Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:42.714349Z"},{"id":"OESA-2025-1560","title":"mod_security security update","description":"This software is also called Modsec,it is an open-source web application firewall. It is designed for Apache HTTP Server.ModSecurity is commonly deployed to provide protections against generic classed of vulnerabilities.The install of this package is easy and you can read the README.TXT for more information.\r\n\r\nSecurity Fix(es):\n\nThe 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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).(CVE-2022-39956)\n\nModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. Versions up to and including 2.9.8 are vulnerable to denial of service in one special case (in stable released versions): when the payload\u0026apos;s content type is `application/json`, and there is at least one rule which does a `sanitiseMatchedBytes` action. A patch is available at pull request 3389 and expected to be part of version 2.9.9. No known workarounds are available.(CVE-2025-47947)","status":"published","published":"2025-05-30T11:08:39Z","modified":"2026-08-18T01:17:58.295180025Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:42.714349Z"},{"id":"OESA-2025-1561","title":"mod_security security update","description":"This software is also called Modsec,it is an open-source web application firewall. It is designed for Apache HTTP Server.ModSecurity is commonly deployed to provide protections against generic classed of vulnerabilities.The install of this package is easy and you can read the README.TXT for more information.\r\n\r\nSecurity Fix(es):\n\nThe 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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).(CVE-2022-39956)\n\nModSecurity is an open source, cross platform web application firewall (WAF) engine for Apache, IIS and Nginx. Versions up to and including 2.9.8 are vulnerable to denial of service in one special case (in stable released versions): when the payload\u0026apos;s content type is `application/json`, and there is at least one rule which does a `sanitiseMatchedBytes` action. A patch is available at pull request 3389 and expected to be part of version 2.9.9. No known workarounds are available.(CVE-2025-47947)","status":"published","published":"2025-05-30T11:08:39Z","modified":"2026-08-18T01:17:58.817163107Z","cvss":[{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T15:52:42.714349Z"},{"id":"UBUNTU-CVE-2022-39956","description":"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 fields that will not be decoded and inspected by the web application firewall engine and the rule set. The multipart payload will therefore bypass detection. A vulnerable backend that supports these encoding schemes can potentially be exploited. The legacy CRS versions 3.0.x and 3.1.x are affected, as well as the currently supported versions 3.2.1 and 3.3.2. Integrators and users are advised upgrade to 3.2.2 and 3.3.3 respectively. The mitigation against these vulnerabilities depends on the installation of the latest ModSecurity version (v2.9.6 / v3.0.8).","status":"published","published":"2022-09-20T07:15:00Z","modified":"2026-10-17T12:55:59.473929939Z","cvss":[{"version":"3.1","score":7.3,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","level":"high"},{"version":"3.1","score":9.8,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"critical"}],"updated_at":"2026-11-02T16:53:55.502114Z"},{"id":"DLA-3293-1","title":"modsecurity-crs - security update","status":"published","published":"2023-01-30T00:00:00Z","modified":"2026-03-09T01:19:21.404288Z","updated_at":"2026-11-02T15:46:11.734021Z"},{"id":"DLA-4265-1","title":"modsecurity-crs - security update","status":"published","published":"2025-08-08T00:00:00Z","modified":"2026-03-09T02:09:08.475104Z","updated_at":"2026-11-02T15:46:12.7027Z"},{"id":"MGASA-2024-0070","title":"Updated apache-mod_security-crs packages fix security vulnerabilities","description":"A SQL injection bypass (aka PL1 bypass) exists in OWASP ModSecurity Core\nRule Set (owasp-modsecurity-crs) through v3.1.0-rc3 via {`a`b} where a\nis a special function name (such as \"if\") and b is the SQL statement to\nbe executed. (CVE-2018-16384)\nModsecurity owasp-modsecurity-crs 3.2.0 (Paranoia level at PL1) has a\nSQL injection bypass vulnerability. Attackers can use the comment\ncharacters and variable assignments in the SQL syntax to bypass\nModsecurity WAF protection and implement SQL injection attacks on Web\napplications. (CVE-2020-22669)\nOWASP ModSecurity Core Rule Set 3.1.x before 3.1.2, 3.2.x before 3.2.1,\nand 3.3.x before 3.3.2 is affected by a Request Body Bypass via a\ntrailing pathname. (CVE-2021-35368)\nThe OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule\nset bypass by submitting a specially crafted HTTP Content-Type header\nfield that indicates multiple character encoding schemes. A vulnerable\nback-end can potentially be exploited by declaring multiple Content-Type\n\"charset\" names and therefore bypassing the configurable CRS\nContent-Type header \"charset\" allow list. An encoded payload can bypass\nCRS detection this way and may then be decoded by the backend.\n(CVE-2022-39955)\nThe OWASP ModSecurity Core Rule Set (CRS) is affected by a partial rule\nset bypass for HTTP multipart requests by submitting a payload that uses\na character encoding scheme via the Content-Type or the deprecated\nContent-Transfer-Encoding multipart MIME header fields that will not be\ndecoded and inspected by the web application firewall engine and the\nrule set. The multipart payload will therefore bypass detection. A\nvulnerable backend that supports these encoding schemes can potentially\nbe exploited. (CVE-2022-39956)\nThe OWASP ModSecurity Core Rule Set (CRS) is affected by a response body\nbypass. A client can issue an HTTP Accept header field containing an\noptional \"charset\" parameter in order to receive the response in an\nencoded form. Depending on the \"charset\", this response can not be\ndecoded by the web application firewall. A restricted resource, access\nto which would ordinarily be detected, may therefore bypass detection.\n(CVE-2022-39957)\nThe OWASP ModSecurity Core Rule Set (CRS) is affected by a response body\nbypass to sequentially exfiltrate small and undetectable sections of\ndata by repeatedly submitting an HTTP Range header field with a small\nbyte range. A restricted resource, access to which would ordinarily be\ndetected, may be exfiltrated from the backend, despite being protected\nby a web application firewall that uses CRS. Short subsections of a\nrestricted resource may bypass pattern matching techniques and allow\nundetected access. (CVE-2022-39958)\n","status":"published","published":"2024-03-18T16:12:23Z","modified":"2026-04-16T04:41:15.500834381Z","updated_at":"2026-11-02T15:49:42.684501Z"}]}}