Bug 2433583 - CVE-2026-24137 gh: sigstore legacy TUF client allows for arbitrary file writes with target cache path traversal [fedora-42]
Summary: CVE-2026-24137 gh: sigstore legacy TUF client allows for arbitrary file write...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gh
Version: 42
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Mikel Olasagasti Uranga
QA Contact:
URL:
Whiteboard: {"flaws": ["a44ea10f-af2b-4305-85db-2...
Depends On:
Blocks: CVE-2026-24137
TreeView+ depends on / blocked
 
Reported: 2026-01-27 21:38 UTC by Jon Moroney
Modified: 2026-03-07 03:32 UTC (History)
4 users (show)

Fixed In Version: gh-2.87.3-1.fc42
Clone Of:
Environment:
Last Closed: 2026-03-07 03:32:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Jon Moroney 2026-01-27 21:38: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-02-27 14:00:59 UTC 
FEDORA-2026-de52e7caa1 (gh-2.87.3-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-de52e7caa1
Comment 2 Fedora Update System 2026-02-28 02:15:16 UTC 
FEDORA-2026-de52e7caa1 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-2026-de52e7caa1`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-de52e7caa1

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2026-03-07 03:32:22 UTC 
FEDORA-2026-de52e7caa1 (gh-2.87.3-1.fc42) has been pushed to the Fedora 42 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.