Bug 2431549 - CVE-2025-59799 ghostscript: From CVEorg collector [fedora-42]
Summary: CVE-2025-59799 ghostscript: From CVEorg collector [fedora-42]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ghostscript
Version: 42
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["e22423f8-4397-4a0e-98cf-a...
Depends On:
Blocks: CVE-2025-59799
TreeView+ depends on / blocked
 
Reported: 2026-01-21 10:32 UTC by Dhananjay Arunesh
Modified: 2026-01-27 06:43 UTC (History)
3 users (show)

Fixed In Version: ghostscript-10.05.1-6.fc42
Clone Of:
Environment:
Last Closed: 2026-01-27 06:43:23 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Dhananjay Arunesh 2026-01-21 10:32: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-01-21 13:29:44 UTC 
FEDORA-2026-d7cbd53e55 (ghostscript-10.05.1-6.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-d7cbd53e55
Comment 2 Fedora Update System 2026-01-22 01:54:44 UTC 
FEDORA-2026-d7cbd53e55 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-d7cbd53e55`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-d7cbd53e55

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2026-01-27 06:43:23 UTC 
FEDORA-2026-d7cbd53e55 (ghostscript-10.05.1-6.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.