Bug 2430433

Summary: CVE-2025-62291 strongswan: From CVEorg collector [epel-10]
Product: [Fedora] Fedora EPEL Reporter: Keith Grant <kgrant>
Component: strongswanAssignee: Paul Wouters <paul.wouters>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: epel10CC: carlosrodrifernandez, davide, michel, paul.wouters, pemensik
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["51435e7e-7559-49f9-8a87-99aef21ca222"]}
Fixed In Version: strongswan-6.0.6-1.el10_3 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2026-06-05 03:48:47 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: 2430429    

Description Keith Grant 2026-01-16 19:41:43 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-05-27 20:15:30 UTC
FEDORA-EPEL-2026-9b6d13e4b9 (strongswan-6.0.6-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-9b6d13e4b9

Comment 2 Fedora Update System 2026-05-28 01:23:12 UTC
FEDORA-EPEL-2026-9b6d13e4b9 has been pushed to the Fedora EPEL 10.3 testing repository.

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

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

Comment 3 Fedora Update System 2026-06-05 03:48:47 UTC
FEDORA-EPEL-2026-9b6d13e4b9 (strongswan-6.0.6-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.