Bug 2494898

Summary:	CVE-2026-25680 gum: golang.org/x/net/html: Denial of Service due to excessive HTML parsing [epel-all]
Product:	[Fedora] Fedora EPEL	Reporter:	jkelly <jkelly>
Component:	gum	Assignee:	Carl George 🤠 <carlwgeorge>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	epel10	CC:	carlwgeorge, go-sig
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["f6764755-9650-40f5-8d06-b9b18511264e"]}
Fixed In Version:	gum-2.0.0-1.el10_4	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-08-24 21:31:26 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:	2480760

Description jkelly 2026-06-30 13:52:21 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.

Parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service.

Comment 1 Fedora Update System 2026-08-24 19:19:00 UTC

FEDORA-EPEL-2026-6a6d19585f (gum-2.0.0-1.el10_4) has been submitted as an update to Fedora EPEL 10.4.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-6a6d19585f

Comment 2 Fedora Update System 2026-08-24 20:04:58 UTC

FEDORA-EPEL-2026-6a6d19585f has been pushed to the Fedora EPEL 10.4 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-6a6d19585f

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

Comment 3 Fedora Update System 2026-08-24 21:31:26 UTC

FEDORA-EPEL-2026-6a6d19585f (gum-2.0.0-1.el10_4) has been pushed to the Fedora EPEL 10.4 stable repository.
If problem still persists, please make note of it in this bug report.