CVE-2025-25184: Possible Log Injection in Rack::CommonLogger
Summary Rack::CommonLogger can be exploited by crafting input that includes newline characters to manipulate log entries. The supplied proof-of-concept demonstrates injecting malicious content into logs. Details When a user provides the authorization credentials via Rack::Auth::Basic, if success, the username will be put in env['REMOTEUSER'] and later be used by Rack::CommonLogger for logging purposes.
Published Feb 12, 2025 · Updated Nov 4, 2025
Affected packages
rack
- Ecosystem
- RubyGems
- Affected
- < 2.2.11
- Fixed in
- 2.2.11
- Check
bundle info rack
rack
- Ecosystem
- RubyGems
- Affected
- >= 3.0, < 3.0.12
- Fixed in
- 3.0.12
- Check
bundle info rack
rack
- Ecosystem
- RubyGems
- Affected
- >= 3.1, < 3.1.10
- Fixed in
- 3.1.10
- Check
bundle info rack
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Rack::CommonLogger can be exploited by crafting input that includes newline characters to manipulate log entries. The supplied proof-of-concept demonstrates injecting malicious content into logs.
Details
When a user provides the authorization credentials via Rack::Auth::Basic, if success, the username will be put in env['REMOTE_USER'] and later be used by Rack::CommonLogger for logging purposes.
The issue occurs when a server intentionally or unintentionally allows a user creation with the username contain CRLF and white space characters, or the server just want to log every login attempts. If an attacker enters a username with CRLF character, the logger will log the malicious username with CRLF characters into the logfile.
Impact
Attackers can break log formats or insert fraudulent entries, potentially obscuring real activity or injecting malicious data into log files.
Mitigation
- Update to the latest version of Rack.
Credited to HexSave, jeremyevans, ioquatix, taketo1113, nick-f, vladimir-mencl-eresearch, lostapathy, matthewbjones, lfittl.
References
- https://github.com/rack/rack/security/advisories/GHSA-7g2v-jj9q-g3rg
- https://nvd.nist.gov/vuln/detail/CVE-2025-25184
- https://github.com/rack/rack/commit/074ae244430cda05c27ca91cda699709cfb3ad8e
- https://github.com/rubysec/ruby-advisory-db/blob/master/gems/rack/CVE-2025-25184.yml
- https://lists.debian.org/debian-lts-announce/2025/03/msg00016.html
- https://github.com/advisories/GHSA-7g2v-jj9q-g3rg
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More RubyGems vulnerabilities
All RubyGems entriesCVE-2026-125108
Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass
low3.7Nov 10, 2026CVE-2026-125109
Rack: Rack::Request#host_with_port (and #base_url / #url) return the raw invalid Host header — incomplete fix of CVE-2026-34835
medium4.8Nov 10, 2026CVE-2026-125110
Rack: Rack::Static header_rules bypass via dot-segment normalization mismatch
medium5.3Nov 10, 2026CVE-2026-125111
Rack: Multipart parsing allows DoS via unbounded scan buffer growth
high7.5Nov 10, 2026CVE-2026-26961
Rack's greedy multipart boundary parsing can cause parser differentials and WAF bypass.
medium5.3Apr 2, 2026CVE-2026-26962
Rack's improper unfolding of folded multipart headers preserves CRLF in parsed parameter values
medium4.8Apr 2, 2026
