Skip to main content
VulnerabilityPublished Updated

CVE-2025-25184: rack · CRLF Injection

Affects rackSource GCVE Database

0
Compare

Public exploit available · CVSS 5.7 Medium · fixed in 3.1.10 : patch rack as a priority.

Data as of 30 Oct 2026, 00:33 UTC

CVSS 4.0 base score
5.7Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.05.7
Patch
Available – fixed in 3.1.10, 3.0.12, 2.2.11
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Feb 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade rack to 3.1.10, 3.0.12 or 2.2.11.

Affected software

ProductAffectedFixed in
rack rackAffected
  • <2.2.11
  • >=3.0 <3.0.12
  • >=3.1 <3.1.10
Fixed in
  • 2.2.11
  • 3.0.12
  • 3.1.10

AI-suggested

Upgrade to Rack versions 2.2.11, 3.0.12, or 3.1.10 or later, where this vulnerability is fixed. No other specific mitigations are indicated by the vendor advisory.

Description

CVE-2025-25184 is a CRLF injection vulnerability in the Rack Ruby web application interface affecting versions prior to 2.2.11, 3.0.12, and 3.1.10. The flaw allows attackers to inject newline characters into log entries via usernames containing CRLF characters when using Rack::Auth::Basic authentication. This can manipulate log files by breaking log formats or inserting fraudulent entries, potentially obscuring legitimate activity. Fixed versions 2.2.11, 3.0.12, and 3.1.10 address this issue.

References

Community reviews

Loading reviews…