Bug 2463216 - CVE-2026-41316 ruby: ERB: Arbitrary code execution via deserialization bypass [fedora-all]
Summary: CVE-2026-41316 ruby: ERB: Arbitrary code execution via deserialization bypass...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ruby
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Vít Ondruch
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["e4c71069-65f4-4ba5-b529-d...
Depends On:
Blocks: CVE-2026-41316
TreeView+ depends on / blocked
 
Reported: 2026-04-27 13:34 UTC by Avinash Hanwate
Modified: 2026-07-18 00:28 UTC (History)
6 users (show)

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


Attachments (Terms of Use)

Description Avinash Hanwate 2026-04-27 13:34:36 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.

Comment 1 Jun Aruga 2026-06-10 10:02:45 UTC
This CVE was fixed on Fedora rawhide (Fedora 45) with ruby-4.0.5-33.fc45 containing erb gem 6.0.1.1 by the PR <https://src.fedoraproject.org/rpms/ruby/pull-request/230>.

CVE-2026-41316
https://github.com/ruby/erb/security/advisories/GHSA-q339-8rmv-2mhv

Comment 2 Jun Aruga 2026-06-10 10:04:59 UTC
The CVE was also fixed on Fedora 44 with ruby-4.0.5-33.fc44.

Comment 3 Jun Aruga 2026-06-10 10:20:26 UTC
The latest Ruby in Fedora 43 is ruby-3.4.8-29.fc43 which contains erb gem 4.0.4. The erb 4.0.4 is still affected by the CVE. The fixed version of erb gem is 4.0.4.1.

Comment 4 Fedora Update System 2026-07-09 12:52:53 UTC
FEDORA-2026-7b7c2b373e (ruby-3.4.10-31.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-7b7c2b373e

Comment 5 Fedora Update System 2026-07-10 01:44:07 UTC
FEDORA-2026-7b7c2b373e has been pushed to the Fedora 43 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-7b7c2b373e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-7b7c2b373e

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

Comment 6 Fedora Update System 2026-07-15 12:28:05 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 7 Fedora Update System 2026-07-15 12:31:19 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 8 Fedora Update System 2026-07-15 12:31:54 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 9 Fedora Update System 2026-07-16 02:18:31 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 10 Fedora Update System 2026-07-18 00:27:07 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.

Comment 11 Fedora Update System 2026-07-18 00:28:02 UTC
FEDORA-2026-7b7c2b373e (ruby-3.4.10-31.fc43) has been pushed to the Fedora 43 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.