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] rawhide: - Update to 152.0.7977.82
Date: Sat, 05 Sep 2026 05:01:46 GMT [thread overview]
Message-ID: <178858450666.1.15151265139003448045.rpms-chromium-32c41f23f562@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/chromium
Branch : rawhide
Commit : 32c41f23f562dd909affb0a8e4ad48c1853303fb
Author : Than Ngo <than@redhat.com>
Date : 2026-09-05T01:00:19-04:00
Stats : +18/-3 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/chromium/c/32c41f23f562dd909affb0a8e4ad48c1853303fb?branch=rawhide
Log:
- Update to 152.0.7977.82
* CVE-2026-85046: Type confusion in V8
* CVE-2026-85052: Out of bounds read in CrashReporting
* CVE-2026-85043: Incomplete cleanup in Network
* CVE-2026-85048: Use after free in Compositing
* CVE-2026-85045: Race condition in V8
* CVE-2026-85050: Out of bounds write in WebGL
* CVE-2026-85053: Improper resource exposure in CacheStorage
* CVE-2026-85042: Use after free in DevTools
* CVE-2026-85049: Use after free in Skia
* CVE-2026-85051: Type confusion in Compositing
* CVE-2026-85047: Improper input validation in Transactions Platform
* CVE-2026-85044: Use of released resource in Mobile
---
diff --git a/chromium.spec b/chromium.spec
index 77a2cd5..aa8a97e 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -271,8 +271,8 @@
%endif
Name: chromium
-Version: 152.0.7977.75
-Release: 2%{?dist}
+Version: 152.0.7977.82
+Release: 1%{?dist}
Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
Url: http://www.chromium.org/Home
License: BSD-3-Clause AND LGPL-2.1-or-later AND Apache-2.0 AND IJG AND MIT AND GPL-2.0-or-later AND ISC AND OpenSSL AND (MPL-1.1 OR GPL-2.0-only OR LGPL-2.0-only)
@@ -1918,6 +1918,21 @@ fi
%endif
%changelog
+* Sat Sep 05 2026 Than Ngo <than@redhat.com> - 152.0.7977.82-1
+- Update to 152.0.7977.82
+ * CVE-2026-85046: Type confusion in V8
+ * CVE-2026-85052: Out of bounds read in CrashReporting
+ * CVE-2026-85043: Incomplete cleanup in Network
+ * CVE-2026-85048: Use after free in Compositing
+ * CVE-2026-85045: Race condition in V8
+ * CVE-2026-85050: Out of bounds write in WebGL
+ * CVE-2026-85053: Improper resource exposure in CacheStorage
+ * CVE-2026-85042: Use after free in DevTools
+ * CVE-2026-85049: Use after free in Skia
+ * CVE-2026-85051: Type confusion in Compositing
+ * CVE-2026-85047: Improper input validation in Transactions Platform
+ * CVE-2026-85044: Use of released resource in Mobile
+
* Thu Sep 03 2026 Dominik Mierzejewski <dominik@greysector.net> - 152.0.7977.75-2
- Rebuilt for FFmpeg 9
diff --git a/sources b/sources
index 38dbf66..8ee19be 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
SHA512 (node-v22.22.0-stripped.tar.gz) = f32a8a73063b3c78cbacf941e11dd529ebcf2618b3ba661966312e49ee9870c43a3acf256e8d331a4b0b621b16a501810c02a3ad763c75884cc250addca8e106
-SHA512 (chromium-152.0.7977.75-clean.tar.xz) = 4278625e10710b8770d1b6a6abddc6fc3e333b693150b780a946e26a51ced63de53105457bc0a9714e8a1cce3b15c33f549ead87e7e700bf747c614aae07e6f5
+SHA512 (chromium-152.0.7977.82-clean.tar.xz) = a944cd30b2fe3f862834c2370ace82dd3192cbc60e1ba4e1581c551db43b852e959b390331990f2dd3674142733dd37694289b39eae614d2d41bf2b59fbd6c8a
reply other threads:[~2026-09-05 5:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=178858450666.1.15151265139003448045.rpms-chromium-32c41f23f562@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