ClassDraft
CWE-185Incorrect Regular Expression
Category: other
Description
The product specifies a regular expression in a way that causes data to be improperly matched or compared.
When the regular expression is used in protection mechanisms such as filtering or validation, this may allow an attacker to bypass the intended restrictions on the incoming data.
Common consequences· 2
- Other — Unexpected State, Varies by ContextWhen the regular expression is not correctly specified, data might have a different format or type than the rest of the program expects, producing resultant weaknesses or errors.
- Access Control — Bypass Protection MechanismIn PHP, regular expression checks can sometimes be bypassed with a null byte, leading to any number of weaknesses.
Potential mitigations· 1
- [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 the 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 the regular expression.
Related CAPEC attack patterns· 3
References
Exploits (incoming)3
| Type | Target | Confidence | Tier |
|---|---|---|---|
| AttackPattern | Using Slashes in Alternate Encodingcapec-79 | 100% | live |
| AttackPattern | Argument Injectioncapec-6 | 100% | live |
| AttackPattern | Command Delimiterscapec-15 | 100% | live |
(incoming)3
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Vulnerability | CVE-2026-25896cve-2026-25896 | 0% | live |
| Vulnerability | CVE-2026-27895cve-2026-27895 | 0% | live |
| Vulnerability | CVE-2026-4296cve-2026-4296 | 0% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.