Base weakness
Draft
RadicalNotion.AILog in
RadicalNotion.AIThe product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.
Last updated
The product may have a fixed list of special characters it believes is complete. However, there may be alternate encodings, or representations that also have the same meaning. For example, the product may filter out a leading slash (/) to prevent absolute path names, but does not account for a tilde (~) followed by a user name, which on some *nix systems could be expanded to an absolute pathname. Alternately, the product might filter a dangerous "-e" command-line switch when calling an external program, but it might not account for "--exec" or other switches that have the same semantics.
11 recorded CVEs are caused by CWE-76 (Improper Neutralization of Equivalent Special Elements). The highest-severity and most recent are shown first. 2 new CWE-76 CVEs have been recorded so far in 2026.
NGINX Ingress Controller vulnerability
NGINX Gateway Fabric vulnerability
What can happen when CWE-76 is exploited.
Other
Affects: Other
Typically introduced during these phases of the software lifecycle.
Practical mitigations for CWE-76, grouped by where in the lifecycle they apply.
Programming languages and supporting technologies might be chosen which are not subject to these issues.
Utilize an appropriate mix of allowlist and denylist parsing to filter equivalent special element syntax from all input.
Common questions about CWE-76.
Weakness data is sourced from the MITRE CWE catalog (v4.20). CVE associations are aggregated and kept current by RadicalNotion.AI.
Get alerted the moment a new CWE-76 vulnerability affects your stack, with AI-written analysis, severity context, and remediation guidance.