CVE-2025-27110
Trustwave Modsecurity 3.0.13
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-27110 is a high-severity Encoding Error (CWE-172) vulnerability in Trustwave Modsecurity. Its CVSS base score is 7.9 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-15 (Information Output Filtering) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-27110 is a vulnerability in Libmodsecurity3 version 3.0.13, a core component of the ModSecurity v3 project that serves as an interface between ModSecurity Connectors and web traffic processing pipelines. The flaw causes the library to fail in decoding HTML entities that contain leading zeroes, stemming from an encoding error classified under CWE-172. This issue is specific to version 3.0.13 and carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).
Remote attackers can exploit this vulnerability over the network with low attack complexity, requiring no privileges, user interaction, or special conditions. Exploitation enables high integrity impact by preventing proper decoding of certain HTML entities, potentially allowing attackers to bypass ModSecurity's traditional web application firewall rules during traffic inspection.
The vulnerability is addressed in Libmodsecurity3 version 3.0.14, which includes a targeted fix. No known workarounds exist. Additional details are available in the ModSecurity GitHub issue (https://github.com/owasp-modsecurity/ModSecurity/issues/3340) and security advisory (https://github.com/owasp-modsecurity/ModSecurity/security/advisories/GHSA-42w7-rmv5-4x2j).
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-5324
Vulnerability Data
Libmodsecurity is one component of the ModSecurity v3 project. The library codebase serves as an interface to ModSecurity Connectors taking in web traffic and applying traditional ModSecurity processing. A bug that exists only in Libmodsecurity3 version 3.0.13 means that, in…
more
3.0.13, Libmodsecurity3 can't decode encoded HTML entities if they contains leading zeroes. Version 3.0.14 contains a fix. No known workarounds are available.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation can reject or normalize improperly encoded data before it is processed.
Output filtering enforces correct encoding or escaping of data leaving the system.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require correct data encoding to avoid injection and corruption flaws.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding explicitly requires correct character encoding and output escaping to avoid CWE-172.
Security testing in development can detect encoding flaws before deployment.
Secure development lifecycle includes input/output validation and encoding practices that reduce encoding errors.
Application security requirements can mandate proper encoding/decoding to prevent data corruption or injection.
Secure system architecture and engineering principles address data handling and transformation correctness.