Bug 2433378

Summary: [Minor Incident] CVE-2025-15467 openssl3: OpenSSL: Remote code execution or Denial of Service via oversized Initialization Vector in CMS parsing [epel-8]
Product: [Fedora] Fedora EPEL Reporter: Patrick Del Bello <pdelbell>
Component: openssl3Assignee: Michel Lind <michel>
Status: CLOSED ERRATA QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: epel8CC: epel-packagers-sig, michel
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["18e7fcac-634f-4eed-9fc8-abade2df4b65"]}
Fixed In Version: openssl3-3.5.5-1.1.el8 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-02-11 00:24:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2430376    

Description Patrick Del Bello 2026-01-27 14:29: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 Fedora Update System 2026-02-02 10:43:14 UTC
FEDORA-EPEL-2026-96a07a6444 (openssl3-3.5.5-1.1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-96a07a6444

Comment 2 Fedora Update System 2026-02-03 03:33:09 UTC
FEDORA-EPEL-2026-96a07a6444 has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-96a07a6444

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

Comment 3 Fedora Update System 2026-02-11 00:24:48 UTC
FEDORA-EPEL-2026-96a07a6444 (openssl3-3.5.5-1.1.el8) has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.