Bug 2431546 - CVE-2025-59800 ghostscript: From CVEorg collector [fedora-43]
Summary: CVE-2025-59800 ghostscript: From CVEorg collector [fedora-43]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ghostscript
Version: 43
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Zdenek Dohnal
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["f38d3839-1934-47a4-bc36-0...
Depends On:
Blocks: CVE-2025-59800
TreeView+ depends on / blocked
 
Reported: 2026-01-21 10:31 UTC by Dhananjay Arunesh
Modified: 2026-01-23 00:55 UTC (History)
3 users (show)

Fixed In Version: ghostscript-10.05.1-6.fc43
Clone Of:
Environment:
Last Closed: 2026-01-23 00:55:42 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2026-01-23 00:55:42 UTC 
FEDORA-2026-c60e345359 (ghostscript-10.05.1-6.fc43) has been pushed to the Fedora 43 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.