Skip to main content
No exploitation reportedFix available

CVE-2021-35368

No exploitation reported by the sources we read.

  • Published2021-11-05
  • Fixed in3.3.2 · 3.2.1 · 3.1.2

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2021-11-0518:15CVE publishedNVD

Versions per branch

NVD
Owasp owasp modsecurity core rule set
BranchAffectedFixed in
3.3≥ 3.3.0, < 3.3.23.3.2
3.2≥ 3.2.0, < 3.2.13.2.1
3.1≥ 3.1.0, < 3.1.23.1.2
Fedoraproject fedora
BranchAffectedFixed in
36.x= 36no fix published
37.x= 37no fix published
Debian debian linux
BranchAffectedFixed in
10.0= 10.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • apache-mod_security-crsMageia:9all versions · fixed in 3.3.5-1.mga9
  • modsecurity-crsUbuntu:26.10all versions · no fixed version listed
  • modsecurity-crsUbuntu:26.04:LTSall versions · no fixed version listed
  • modsecurity-crsUbuntu:25.10all versions · no fixed version listed
  • modsecurity-crsUbuntu:24.04:LTSall versions · no fixed version listed
  • modsecurity-crsUbuntu:22.04:LTSall versions · no fixed version listed
  • modsecurity-crsUbuntu:20.04:LTSall versions · no fixed version listed
  • modsecurity-crsUbuntu:18.04:LTSall versions · no fixed version listed

4 more package ranges on OSV.dev

Vendor advisories

  • CVE-2021-35368 Red Hat Product Security

    libmodsecurity: request body bypass via a trailing pathname

Full record on NVD

Fix

  1. Update Owasp owasp modsecurity core rule set to 3.3.2 · 3.2.1 · 3.1.2

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2021-11-05
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-2xw7-44j9-24rv

Frequently asked questions

What is CVE-2021-35368?

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.

Is CVE-2021-35368 actively exploited?

Active exploitation of CVE-2021-35368 has not been confirmed. Its EPSS score was 2.7% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2021-35368?

CVE-2021-35368 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running libmodsecurity? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record