WAF rule bypass via truncated Unicode transformation
Published Jul 10, 2026 · Updated Jul 10, 2026
Rule bypass in OWASP ModSecurity 3.0.0 through 3.0.15 allows remote attackers to evade WAF inspection via crafted UTF-8 input. In src/actions/transformations/utf8_to_unicode.cc, snprintf receives the size of a char pointer instead of the Unicode buffer length, truncating transformed output on i386. Only i386 deployments whose rules use t:utf8toUnicode are exposed; affected rules can miss malicious request content while other architectures are unaffected.
Summary
What happened
Rule bypass in OWASP ModSecurity 3.0.0 through 3.0.15 allows remote attackers to evade WAF inspection via crafted UTF-8 input. In src/actions/transformations/utf8_to_unicode.cc, snprintf receives the size of a char pointer instead of the Unicode buffer length, truncating transformed output on i386. Only i386 deployments whose rules use t:utf8toUnicode are exposed; affected rules can miss malicious request content while other architectures are unaffected.
The record
- CVE
- CVE-2026-52761
- Published
- Jul 10, 2026
- Updated
- Jul 10, 2026
- Vendor
- OWASP ModSecurity
- Product
- ModSecurity
- Classifications
- CWE-467, T1562.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 10, 2026CVE publishedPublication date reported by the CVE source.
- Jul 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.0.0, < 3.0.16
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo