CWE-186: Overly Restrictive Regular Expression
2 CVEs have CWE-186 as their primary weakness. 0 of them are in the CISA KEV catalog. The highest EPSS score among them is 0.482%.
A regular expression is overly restrictive in a way that does not match all intended values.
Child of CWE-185: Incorrect Regular Expression
Mitigations
- Implementation: Regular expressions can become error prone when defining a complex language even for those experienced in writing grammars. Determine if several smaller regular expressions simplify one large regular expression. Also, subject your regular expression to thorough testing techniques such as equivalence partitioning, boundary value analysis, and robustness. After testing and a reasonable confidence level is achieved, a regular expression may not be foolproof. If an exploit is allowed to slip through, then record the exploit and refactor your regular expression.
Observed examples
- CVE-2005-1604: MIE. .php.ns bypasses .php$ regexp but is still parsed as PHP by Apache. (manipulates an equivalence property under Apache)
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-186'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-186'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).