{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33691 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-33691 is a medium-severity vulnerability in coreruleset, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33691 and fix it if it is affected.\n\nWhat it is: CVE-2026-33691 is a medium-severity vulnerability in coreruleset, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33691 in the wild and no public exploit code.\n\nAffected product: coreruleset. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33691/ (Markdown: https://insights.sbomify.com/CVE-2026-33691/index.md)","id":"CVE-2026-33691","markdown":"https://insights.sbomify.com/CVE-2026-33691/index.md","name":"CVE-2026-33691","record":{"aliases":["DEBIAN-CVE-2026-33691","GHSA-rw5f-9w43-gv2w","UBUNTU-CVE-2026-33691","openSUSE-SU-2026:11632-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Web Application Firewall","requires_auth":"none","summary":"Attackers can upload malicious files with dangerous extensions by using whitespace padding, bypassing OWASP CRS file upload checks.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"owasp_modsecurity_core_rule_set","vendor":"owasp"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-178","name":"Improper Handling of Case Sensitivity"}],"description":"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.","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"OWASP CRS: Whitespace padding in filenames bypasses file upload extension checks","id":"CVE-2026-33691","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":1,"n_references":7,"next":{"headline":"AVideo Has Unauthenticated .env File Exposure via Official Docker Compose Configuration","id":"CVE-2026-33692"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["4.29.0-1.1"],"introduced":["0"],"last_affected":[],"package":"owasp-modsecurity-crs","purl":"pkg:rpm/opensuse/owasp-modsecurity-crs\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:11632-1"}],"prev":{"headline":"AVideo vulnerable to IP Address Spoofing via Untrusted HTTP Headers in getRealIpAddr()","id":"CVE-2026-33690"},"products":["coreruleset"],"published":"2026-04-02","related":[{"cvss_score":9.3,"headline":"OWASP CRS has multipart bypass using multiple content-type parts","id":"CVE-2026-21876","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2018-16384","kev_date_added":null,"published":"2018-09-03"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-18","vendors":["coreruleset"]},"summary":"Attackers can upload malicious files with dangerous extensions by using whitespace padding, bypassing OWASP CRS file upload checks.","url":"https://insights.sbomify.com/CVE-2026-33691/"}