Servers and applications
GHSA-4j47-8qcr-jf59
`t:base64DecodeExt` silently discards the entire decoded value on a malformed base64 padding group, bypassing rule matching
- Severity
- Medium 5.8
- Published
- 30 Sept 2026
- Last changed
- 30 Sept 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 2.9.15, 3.0.17
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N- Sources
- Project advisories (GitHub)
Description
t:base64DecodeExt (and the shared decode engine behind it, decode_forgiven_engine in v3 / decode_base64_ext in v2) discards the entire decoded output — not just the malformed portion — whenever the input contains a base64 group with a single leftover data character immediately before == padding (e.g. ...V==), which can occur anywhere in the string. The transformation still reports success (changed=true / a non-zero return), giving no signal that anything went wrong. Any rule that applies t:base64DecodeExt to attacker-controlled input and then matches against the decoded content can be defeated by appending or inserting a throwaway malformed padding group (e.g. A==) anywhere in the value — the real, otherwise-detectable payload decodes to an empty string and the rule never sees it.
This is more broadly exploitable than a related, already-known-internally base64url-alphabet issue (-/_ handling) in the same function, because it requires no url-safe-alphabet characters at all — just one…
Affected software
| Software | Affected versions |
|---|---|
ModSecurityServers and applications · github:owasp-modsecurity/modsecurity |
|
About ModSecurity
web application firewall (WAF) module
- Docker Hub pulls
- 7,086,565Docker Hub, 15 Nov 2026
- GitHub stars
- 9,872GitHub, 15 Nov 2026
- Forks
- 1,761GitHub, 15 Nov 2026
- Latest release
- v3.0.17GitHub, 15 Nov 2026
- Released
- 29 Sept 2026GitHub
- Developer
- Trustwave HoldingsWikidata
- License
- Apache Software License 2.0Wikidata
- Written in
- CWikidata
- First published on GitHub
- 2 Feb 2011GitHub
Website Source code Docker image
Vulnerabilities in ModSecurity
- In our list
- 36
- Published in the last 12 months
- 12
- Critical, last 12 months
- 0
- High, last 12 months
- 6
- Known exploited
- 0
- CVE-2026-61813ModSecurity: Incorrect libcurl TLS hostname verification setting in HttpsClient::downloadLow 3.7 5 Nov 2026
- CVE-2026-104269RFC 2231 `filename*` Parameter Bypasses Multipart Filename Rules on RFC-Compliant Backends (Go, Python, Node, Java)High 8.6 30 Sept 2026
- CVE-2026-104259removeComments Transformation Fails to Strip Adjacent Comments, Enabling WAF Rule BypassMedium 5.4 30 Sept 2026
- CVE-2026-103932PCRE2 `@rxGlobal` match-limit errors are converted to no-matchMedium 5.8 30 Sept 2026
- CVE-2026-73857ModSecurity v3 XML Request Body Processor Uninitialized Pointer Dereference VulnerabilityHigh 7.5 30 Sept 2026
- CVE-2026-73856Response Body Inspection BypassHigh 8.6 30 Sept 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-4j47-8qcr-jf59
- github.com https://github.com/owasp-modsecurity/ModSecurity/security/advisories/GHSA-4j47-8qcr-jf59