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] f43: - Update to 150.0.7871.186
Date: Fri, 24 Jul 2026 14:01:28 GMT	[thread overview]
Message-ID: <178490168884.1.893376275636810149.rpms-chromium-417666f8097e@fedoraproject.org> (raw)

          A new commit has been pushed.

          Repo   : rpms/chromium
          Branch : f43
          Commit : 417666f8097eb659677731dcca055986900d0162
          Author : Than Ngo <than@redhat.com>
          Date   : 2026-07-24T14:37:33+02:00
          Stats  : +9/-2 in 2 file(s)
          URL    : https://src.fedoraproject.org/rpms/chromium/c/417666f8097eb659677731dcca055986900d0162?branch=f43

          Log:
          - Update to 150.0.7871.186
* CVE-2026-16807: Out of bounds write in Codecs
* CVE-2026-16806: Use after free in WebMCP
* CVE-2026-16805: Use after free in Blink
* CVE-2026-16804: Use after free in Input

---
diff --git a/chromium.spec b/chromium.spec
index 10d32d6..f77a55d 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -271,7 +271,7 @@
 %endif
 
 Name:	chromium
-Version: 150.0.7871.181
+Version: 150.0.7871.186
 Release: 1%{?dist}
 Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
 Url: http://www.chromium.org/Home
@@ -1922,6 +1922,13 @@ fi
 %endif
 
 %changelog
+* Fri Jul 24 2026 Than Ngo <than@redhat.com> - 150.0.7871.186-1
+- Update to 150.0.7871.186
+  * CVE-2026-16807: Out of bounds write in Codecs
+  * CVE-2026-16806: Use after free in WebMCP
+  * CVE-2026-16805: Use after free in Blink
+  * CVE-2026-16804: Use after free in Input
+
 * Wed Jul 22 2026 Than Ngo <than@redhat.com> - 150.0.7871.181-1
 - Update to 150.0.7871.181
   * CVE-2026-16413: Out of bounds write in ANGLE

diff --git a/sources b/sources
index e0ab696..6dd4671 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
 SHA512 (node-v22.22.0-stripped.tar.gz) = f32a8a73063b3c78cbacf941e11dd529ebcf2618b3ba661966312e49ee9870c43a3acf256e8d331a4b0b621b16a501810c02a3ad763c75884cc250addca8e106
-SHA512 (chromium-150.0.7871.181-clean.tar.xz) = 31dd4e848780ef062d5a7a0484b9c602bda0c7bcbe8a865e91803ebd561f9db66882e3a659249b892970a68c6e0a844fc59e8959961d749063d672c6236df09c
+SHA512 (chromium-150.0.7871.186-clean.tar.xz) = c217d1ae0a5601c42f92997af527426b5f7ef827519909725166c5ab3c02366c5deffd56324017b4b7961b269877b64af515b26edab86d7a225a7e6e1aca5e0f

                 reply	other threads:[~2026-07-24 14: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=178490168884.1.893376275636810149.rpms-chromium-417666f8097e@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