On this page

CWE-185: Incorrect Regular Expression

Weakness Summary

The product specifies a regular expression in a way that causes data to be improperly matched or compared.

  • Canonical source: MITRE CWE-185
  • Published Atomicorp CVE observations: 1
  • Distinct affected products in those observations: 1
  • Active Atomicorp rules associated with this weakness: 12

Atomicorp Research Context

Atomicorp has published CVE-specific research observations associated with this weakness category. Each linked CVE page states whether the tested request was detected or blocked and is the authoritative customer-facing finding.

The CVEs and rules shown here are selected published examples, not a complete list of Atomicorp protections. If a CWE, CVE, or rule is absent from this page, no conclusion should be drawn about whether Atomicorp protects against that weakness or attack method.

A CWE describes a class of software weakness. It does not identify one exploit request, and association with a CWE does not mean that every vulnerability or exploitation path in that category is detected or blocked.

Selected Published CVE Observations

CVEVulnerabilityProductAtomicorp findingObserved rules
CVE-2026-54506Vvveb: Stored XSS via sanitizeHTML() bypass in user profile bio fieldVvvebProtected by Atomicorp rules333140 , 333141 , 340095 , 340147 , 340148 , 340247 , 340248 , 341256 , 342259 , 346755 , 350147 , 350148

Associated Atomicorp WAF Rules

RuleStatusBehavior
333140Activedisruptive (deny)
333141Activedisruptive (deny)
340095Activedisruptive (deny)
340147Activedisruptive (deny)
340148Activedisruptive (deny)
340247Activedisruptive (deny)
340248Activedisruptive (deny)
341256Activedisruptive (deny)
342259Activedisruptive (deny)
346755Activedisruptive (deny)
350147Activedisruptive (deny)
350148Activedisruptive (deny)

MITRE associates this CWE with the following attack-pattern entries. These taxonomy relationships are context, not Atomicorp coverage claims:

CAPEC-15 , CAPEC-6 , CAPEC-79