Bug 2498917 - CVE-2026-47240 ruby: Net::IMAP: Command injection via non-synchronizing literals [fedora-all]
Summary: CVE-2026-47240 ruby: Net::IMAP: Command injection via non-synchronizing liter...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ruby
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["2687d809-4886-4a69-a994-0...
Depends On:
Blocks: CVE-2026-47240
TreeView+ depends on / blocked
 
Reported: 2026-07-10 07:36 UTC by Marian Rehak
Modified: 2026-07-18 00:27 UTC (History)
5 users (show)

Fixed In Version: ruby-4.0.6-36.fc44
Clone Of:
Environment:
Last Closed: 2026-07-18 00:27:24 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Marian Rehak 2026-07-10 07:36:40 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Net::IMAP implements Internet Message Access Protocol (IMAP) client functionality in Ruby. Prior to 0.6.5 and 0.5.15, several Net::IMAP commands accept a "raw data" argument that is sent verbatim after validation to prevent command injection. However, if a server does not support non-synchronizing literals, it may still be possible to inject arbitrary IMAP commands inside non-synchronizing literals.  A server without support for non-synchronizing literals may interpret the "+}\r\n" as the end of a malformed command line and respond with a tagged BAD. In that case, the contents of the literal will be interpreted as one or more new pipelined commands, allowing a CRLF command injection attack to succeed. This affects criteria for #search and #uid_search; search_keys for #sort, #thread, #uid_sort, and #uid_thread; and attr for #fetch and #uid_fetch. This vulnerability is fixed in 0.6.5 and 0.5.15.

Comment 1 Mamoru TASAKA 2026-07-10 14:48:02 UTC
F-43 ruby updates (currently in -testing) ruby-3.4.10-31.fc43 already contains fix for this CVE entry.

Comment 2 Fedora Update System 2026-07-15 12:28:19 UTC
FEDORA-2026-7f499e0362 (ruby-4.0.6-36.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-7f499e0362

Comment 3 Fedora Update System 2026-07-15 12:31:32 UTC
FEDORA-2026-32d5a3d450 (ruby-4.0.6-36.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-32d5a3d450

Comment 4 Fedora Update System 2026-07-15 12:32:04 UTC
FEDORA-2026-7f499e0362 (ruby-4.0.6-36.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2026-07-16 02:18:41 UTC
FEDORA-2026-32d5a3d450 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-32d5a3d450`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-32d5a3d450

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-07-18 00:27:24 UTC
FEDORA-2026-32d5a3d450 (ruby-4.0.6-36.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.