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:08:53 GMT [thread overview]
Message-ID: <178611893371.1.4058302318991434009.rpms-chromium-df91226ef27c@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : epel9-next
Commit : df91226ef27c12ce770b59394c317400de93d639
Author : Than Ngo <than@redhat.com>
Date : 2026-04-09T08:55:59+02:00
Stats : +61/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/df91226ef27c12ce770b59394c317400de93d639?branch=epel9-next
Log:
Add CVEs in changelog
---
diff --git a/chromium.spec b/chromium.spec
index 30bf5a4..b56c83b 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -1857,8 +1857,68 @@ fi
%endif
%changelog
-* Wed Apr 08 2026 Than Ngo <than@redhat.com> - 147.0.7727.55-1
+* Thu Apr 09 2026 Than Ngo <than@redhat.com> - 147.0.7727.55-1
- Update to 147.0.7727.55
+ * Critical CVE-2026-5858: Heap buffer overflow in WebML
+ * Critical CVE-2026-5859: Integer overflow in WebML
+ * High CVE-2026-5860: Use after free in WebRTC
+ * High CVE-2026-5861: Use after free in V8
+ * High CVE-2026-5862: Inappropriate implementation in V8
+ * High CVE-2026-5863: Inappropriate implementation in V8
+ * High CVE-2026-5864: Heap buffer overflow in WebAudio
+ * High CVE-2026-5865: Type Confusion in V8
+ * High CVE-2026-5866: Use after free in Media
+ * High CVE-2026-5867: Heap buffer overflow in WebML
+ * High CVE-2026-5868: Heap buffer overflow in ANGLE
+ * High CVE-2026-5869: Heap buffer overflow in WebML
+ * High CVE-2026-5870: Integer overflow in Skia
+ * High CVE-2026-5871: Type Confusion in V8
+ * High CVE-2026-5872: Use after free in Blink
+ * High CVE-2026-5873: Out of bounds read and write in V8
+ * Medium CVE-2026-5874: Use after free in PrivateAI
+ * Medium CVE-2026-5875: Policy bypass in Blink
+ * Medium CVE-2026-5876: Side-channel information leakage in Navigation
+ * Medium CVE-2026-5877: Use after free in Navigation
+ * Medium CVE-2026-5878: Incorrect security UI in Blink
+ * Medium CVE-2026-5879: Insufficient validation of untrusted input in ANGLE
+ * Medium CVE-2026-5880: Incorrect security UI in browser UI
+ * Medium CVE-2026-5881: Policy bypass in LocalNetworkAccess
+ * Medium CVE-2026-5882: Incorrect security UI in Fullscreen
+ * Medium CVE-2026-5883: Use after free in Media
+ * Medium CVE-2026-5884: Insufficient validation of untrusted input in Media
+ * Medium CVE-2026-5885: Insufficient validation of untrusted input in WebML
+ * Medium CVE-2026-5886: Out of bounds read in WebAudio
+ * Medium CVE-2026-5887: Insufficient validation of untrusted input in Downloads
+ * Medium CVE-2026-5888: Uninitialized Use in WebCodecs
+ * Medium CVE-2026-5889: Cryptographic Flaw in PDFium
+ * Medium CVE-2026-5890: Race in WebCodecs
+ * Medium CVE-2026-5891: Insufficient policy enforcement in browser UI
+ * Medium CVE-2026-5892: Insufficient policy enforcement in PWAs
+ * Medium CVE-2026-5893: Race in V8
+ * Low CVE-2026-5894: Inappropriate implementation in PDF
+ * Low CVE-2026-5895: Incorrect security UI in Omnibox
+ * Low CVE-2026-5896: Policy bypass in Audio
+ * Low CVE-2026-5897: Incorrect security UI in Downloads
+ * Low CVE-2026-5898: Incorrect security UI in Omnibox
+ * Low CVE-2026-5899: Incorrect security UI in History Navigation
+ * Low CVE-2026-5900: Policy bypass in Downloads
+ * Low CVE-2026-5901: Policy bypass in DevTools
+ * Low CVE-2026-5902: Race in Media
+ * Low CVE-2026-5903: Policy bypass in IFrameSandbox
+ * Low CVE-2026-5904: Use after free in V8
+ * Low CVE-2026-5905: Incorrect security UI in Permissions
+ * Low CVE-2026-5906: Incorrect security UI in Omnibox
+ * Low CVE-2026-5907: Insufficient data validation in Media
+ * Low CVE-2026-5908: Integer overflow in Media
+ * Low CVE-2026-5909: Integer overflow in Media
+ * Low CVE-2026-5910: Integer overflow in Media
+ * Low CVE-2026-5911: Policy bypass in ServiceWorkers
+ * Low CVE-2026-5912: Integer overflow in WebRTC
+ * Low CVE-2026-5913: Out of bounds read in Blink
+ * Low CVE-2026-5914: Type Confusion in CSS
+ * Low CVE-2026-5915: Insufficient validation of untrusted input in WebML
+ * Low CVE-2026-5918: Inappropriate implementation in Navigation
+ * Low CVE-2026-5919: Insufficient validation of untrusted input in WebSockets
* Wed Apr 01 2026 Than Ngo <than@redhat.com> - 146.0.7680.177-1
- Update to 146.0.7680.177
next reply other threads:[~2026-08-07 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 16:08 Than Ngo [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-08-07 16:09 [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=178611893371.1.4058302318991434009.rpms-chromium-df91226ef27c@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