Bug 2529713 - CVE-2026-79220 chromium: Google Chrome: Information leak via crafted HTML page [fedora-all]
Summary: CVE-2026-79220 chromium: Google Chrome: Information leak via crafted HTML pag...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["740e16c2-3f2c-4f0a-a14d-e...
Depends On:
Blocks: CVE-2026-79220
TreeView+ depends on / blocked
 
Reported: 2026-09-08 08:32 UTC by Dhananjay Arunesh
Modified: 2026-09-19 01:00 UTC (History)
6 users (show)

Fixed In Version: chromium-153.0.8010.36-1.fc44 chromium-153.0.8010.36-1.fc45 chromium-153.0.8010.36-1.el10_3 chromium-153.0.8010.36-1.el10_4 chromium-153.0.8010.36-1.fc43 chromium-153.0.8010.36-1.el10_2
Clone Of:
Environment:
Last Closed: 2026-09-18 01:16:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Dhananjay Arunesh 2026-09-08 08:32:08 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.

Information leak in Network in Google Chrome prior to 152.0.7977.65 allowed a remote attacker who had compromised the renderer process to obtain sensitive information via a crafted HTML page. (Chromium security severity: Medium)

Comment 1 Fedora Update System 2026-09-17 06:19:16 UTC
FEDORA-EPEL-2026-d7f643de0b (chromium-153.0.8010.36-1.el10_4) has been submitted as an update to Fedora EPEL 10.4.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-d7f643de0b

Comment 2 Fedora Update System 2026-09-17 06:19:17 UTC
FEDORA-2026-6932094a69 (chromium-153.0.8010.36-1.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-6932094a69

Comment 3 Fedora Update System 2026-09-17 06:19:18 UTC
FEDORA-2026-a1a12d9b4f (chromium-153.0.8010.36-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-a1a12d9b4f

Comment 4 Fedora Update System 2026-09-17 06:19:19 UTC
FEDORA-EPEL-2026-eeb82ef938 (chromium-153.0.8010.36-1.el10_3) has been submitted as an update to Fedora EPEL 10.3.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2026-eeb82ef938

Comment 5 Fedora Update System 2026-09-17 06:19:20 UTC
FEDORA-2026-441ccd8509 (chromium-153.0.8010.36-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-441ccd8509

Comment 6 Fedora Update System 2026-09-18 01:16:33 UTC
FEDORA-2026-441ccd8509 (chromium-153.0.8010.36-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 7 Fedora Update System 2026-09-18 01:32:55 UTC
FEDORA-2026-a1a12d9b4f 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-a1a12d9b4f`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-a1a12d9b4f

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

Comment 8 Fedora Update System 2026-09-18 01:44:03 UTC
FEDORA-EPEL-2026-dff966929c has been pushed to the Fedora EPEL 10.2 testing repository.

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

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

Comment 9 Fedora Update System 2026-09-18 01:51:31 UTC
FEDORA-EPEL-2026-d7f643de0b 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-d7f643de0b

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

Comment 10 Fedora Update System 2026-09-18 01:57:54 UTC
FEDORA-EPEL-2026-eeb82ef938 has been pushed to the Fedora EPEL 10.3 testing repository.

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

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

Comment 11 Fedora Update System 2026-09-18 01:58:06 UTC
FEDORA-2026-6932094a69 has been pushed to the Fedora 45 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-6932094a69`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-6932094a69

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

Comment 12 Fedora Update System 2026-09-19 00:17:21 UTC
FEDORA-2026-6932094a69 (chromium-153.0.8010.36-1.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2026-09-19 00:31:16 UTC
FEDORA-EPEL-2026-eeb82ef938 (chromium-153.0.8010.36-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2026-09-19 00:43:06 UTC
FEDORA-EPEL-2026-d7f643de0b (chromium-153.0.8010.36-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.

Comment 15 Fedora Update System 2026-09-19 00:58:25 UTC
FEDORA-2026-a1a12d9b4f (chromium-153.0.8010.36-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 16 Fedora Update System 2026-09-19 01:00:18 UTC
FEDORA-EPEL-2026-dff966929c (chromium-153.0.8010.36-1.el10_2) has been pushed to the Fedora EPEL 10.2 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.