Bug 2397973

Summary: CVE-2025-59343 yarnpkg: tar-fs symlink validation bypass [fedora-42]
Product: [Fedora] Fedora Reporter: Jon Moroney <jmoroney>
Component: yarnpkgAssignee: Neal Gompa <ngompa13>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 42CC: epel-packagers-sig, manisandro, ngompa13
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["871a1446-ae2e-4341-8f99-ec282c149078"]}
Fixed In Version: yarnpkg-1.22.22-12.fc42 yarnpkg-1.22.22-12.fc41 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-10-09 00:50:49 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: 2397901    

Description Jon Moroney 2025-09-24 20:57:19 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-09-30 22:20:01 UTC
FEDORA-2025-4dd58248ff (yarnpkg-1.22.22-12.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-4dd58248ff

Comment 2 Fedora Update System 2025-09-30 22:20:04 UTC
FEDORA-2025-ee9e7fb981 (yarnpkg-1.22.22-12.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-ee9e7fb981

Comment 3 Fedora Update System 2025-09-30 22:20:08 UTC
FEDORA-2025-418da1e0e6 (yarnpkg-1.22.22-12.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-418da1e0e6

Comment 4 Fedora Update System 2025-10-01 15:21:40 UTC
FEDORA-2025-418da1e0e6 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-418da1e0e6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-418da1e0e6

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

Comment 5 Fedora Update System 2025-10-01 15:56:14 UTC
FEDORA-2025-4dd58248ff has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-4dd58248ff`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-4dd58248ff

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

Comment 6 Fedora Update System 2025-10-01 16:01:11 UTC
FEDORA-2025-ee9e7fb981 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-2025-ee9e7fb981`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-ee9e7fb981

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

Comment 7 Fedora Update System 2025-10-09 00:50:49 UTC
FEDORA-2025-418da1e0e6 (yarnpkg-1.22.22-12.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-10-09 01:15:28 UTC
FEDORA-2025-4dd58248ff (yarnpkg-1.22.22-12.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.