Bug 2408084

Summary: CVE-2025-58189 podman: go crypto/tls ALPN negotiation error contains attacker controlled information [fedora-42]
Product: [Fedora] Fedora Reporter: Jon Moroney <jmoroney>
Component: podmanAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 42CC: bbaude, debarshir, dwalsh, go-sig, jnovy, lsm5, mboddu, mheon, nsella, patrick, pholzing, suraj.ghimire7
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["3315d28f-56bc-48ea-9391-3ff13568ea24"]}
Fixed In Version: podman-5.7.0-1.fc42 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-11-25 01:35:12 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: 2407260    

Description Jon Moroney 2025-10-30 19:41: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.

The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams
Comment 1 Fedora Update System 2025-11-12 13:50:21 UTC 
FEDORA-2025-8a248ee4f4 (buildah-1.42.1-1.fc42 and podman-5.7.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-8a248ee4f4
Comment 2 Fedora Update System 2025-11-25 01:35:12 UTC 
FEDORA-2025-8a248ee4f4 (buildah-1.42.1-1.fc42 and podman-5.7.0-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.