Bug 2432198

Summary:	CVE-2026-23831 gh: Rekor denial of service [fedora-43]
Product:	[Fedora] Fedora	Reporter:	Jon Moroney <jmoroney>
Component:	gh	Assignee:	Mikel Olasagasti Uranga <mikel>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	43	CC:	go-sig, maxwell, mikel, suraj.ghimire7
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["5038f6a5-4020-419c-8e05-af1aa2738423"]}
Fixed In Version:	gh-2.87.0-2.fc43	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-02-27 00:54:30 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:	2432169

Description Jon Moroney 2026-01-22 22:38:12 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-18 22:20:42 UTC

FEDORA-2026-21a2f3709a (gh-2.87.0-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-21a2f3709a

Comment 2 Fedora Update System 2026-02-19 00:53:28 UTC

FEDORA-2026-21a2f3709a 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-21a2f3709a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-21a2f3709a

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

Comment 3 Fedora Update System 2026-02-27 00:54:30 UTC

FEDORA-2026-21a2f3709a (gh-2.87.0-2.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.