public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: Add CVEs in changelog
Date: Fri, 07 Aug 2026 16:09:04 GMT [thread overview]
Message-ID: <178611894429.1.15889926501505763026.rpms-chromium-44503fc3bf73@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : 44503fc3bf73721e282b91569c05d19967d30a30
Author : Than Ngo <than@redhat.com>
Date : 2026-05-21T08:35:46+02:00
Stats : +16/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/44503fc3bf73721e282b91569c05d19967d30a30?branch=epel9-next
Log:
Add CVEs in changelog
* CVE-2026-9111: Use after free in WebRTC
* CVE-2026-9110: Inappropriate implementation in UI
* CVE-2026-9112: Use after free in GPU
* CVE-2026-9113: Out of bounds read in GPU
* CVE-2026-9114: Use after free in QUIC
* CVE-2026-9115: Insufficient policy enforcement in Service Worker
* CVE-2026-9116: Insufficient policy enforcement in ServiceWorker
* CVE-2026-9117: Type Confusion in GFX
* CVE-2026-9118: Use after free in XR
* CVE-2026-9119: Heap buffer overflow in WebRTC
* CVE-2026-9120: Use after free in WebRTC
* CVE-2026-9126: Use after free in DOM
* CVE-2026-9121: Out of bounds read in GPU
* CVE-2026-9122: Out of bounds read in GPU
* CVE-2026-9123: Heap buffer overflow in Chromecast
* CVE-2026-9124: Insufficient validation of untrusted input in Input
---
diff --git a/chromium.spec b/chromium.spec
index 3f289ae..2a1d7d5 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -1893,6 +1893,22 @@ fi
%changelog
* Wed May 20 2026 Than Ngo <than@redhat.com> - 148.0.7778.178-1
- Update to 148.0.7778.178
+ * CVE-2026-9111: Use after free in WebRTC
+ * CVE-2026-9110: Inappropriate implementation in UI
+ * CVE-2026-9112: Use after free in GPU
+ * CVE-2026-9113: Out of bounds read in GPU
+ * CVE-2026-9114: Use after free in QUIC
+ * CVE-2026-9115: Insufficient policy enforcement in Service Worker
+ * CVE-2026-9116: Insufficient policy enforcement in ServiceWorker
+ * CVE-2026-9117: Type Confusion in GFX
+ * CVE-2026-9118: Use after free in XR
+ * CVE-2026-9119: Heap buffer overflow in WebRTC
+ * CVE-2026-9120: Use after free in WebRTC
+ * CVE-2026-9126: Use after free in DOM
+ * CVE-2026-9121: Out of bounds read in GPU
+ * CVE-2026-9122: Out of bounds read in GPU
+ * CVE-2026-9123: Heap buffer overflow in Chromecast
+ * CVE-2026-9124: Insufficient validation of untrusted input in Input
- Backport upstream patches to improve auto dark image inversion logic
- Update default chromium browser config
next reply other threads:[~2026-08-07 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 16:09 Than Ngo [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-07 16:08 [rpms/chromium] epel9-next: Add CVEs in changelog Than Ngo
2026-08-07 16:08 Than Ngo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178611894429.1.15889926501505763026.rpms-chromium-44503fc3bf73@fedoraproject.org \
--to=than@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox