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/cef] rawhide: Update to 151.0.7922.173
Date: Fri, 04 Sep 2026 17:42:57 GMT	[thread overview]
Message-ID: <178854377732.1.17199232464259785700.rpms-cef-6488ba1c5bc1@fedoraproject.org> (raw)

          A new commit has been pushed.

          Repo   : rpms/cef
          Branch : rawhide
          Commit : 6488ba1c5bc1127d21fece810f7fd1c5036d27b0
          Author : Than Ngo <than@redhat.com>
          Date   : 2026-09-04T17:42:13+00:00
          Stats  : +2/-2 in 2 file(s)
          URL    : https://src.fedoraproject.org/rpms/cef/c/6488ba1c5bc1127d21fece810f7fd1c5036d27b0?branch=rawhide

          Log:
          Update to 151.0.7922.173
* CVE-2026-76017: Use after free in Chromoting
* CVE-2026-76018: Privilege elevation in Import
* CVE-2026-76019: Incorrect authorization in Workers
* CVE-2026-76020: Race condition in V8
* CVE-2026-76021: Use after free in DOM
* CVE-2026-76022: Buffer overflow in Network
* CVE-2026-76023: Improper resource control in Linux Toolkit Theming

---
diff --git a/cef.spec b/cef.spec
index 6fe9c6a..5045f4b 100644
--- a/cef.spec
+++ b/cef.spec
@@ -247,7 +247,7 @@
 %global chromium_major 151
 %global chromium_branch 7922
 # Where possible, track Chromium versions already released in Fedora.
-%global chromium_minor 169
+%global chromium_minor 173
 %global chromium_version %{chromium_major}.0.%{chromium_branch}.%{chromium_minor}
 %global cef_commit 3a0fcf1e1b6249b50c96ac77c429bfefade09d96
 %global cef_branch %{chromium_branch}

diff --git a/sources b/sources
index 0745e7c..d054922 100644
--- a/sources
+++ b/sources
@@ -1,3 +1,3 @@
 SHA512 (3a0fcf1e1b6249b50c96ac77c429bfefade09d96.tar.gz) = 450ad00c41029796629edebeb7f589ce4f206c8ffcca55dd6900420cca0aabea869e4dd1996bafff3084b5ab14466bf579486c525bd16a49f5e5a62635736972
 SHA512 (node-v22.22.0-stripped.tar.gz) = f32a8a73063b3c78cbacf941e11dd529ebcf2618b3ba661966312e49ee9870c43a3acf256e8d331a4b0b621b16a501810c02a3ad763c75884cc250addca8e106
-SHA512 (chromium-151.0.7922.169-clean.tar.xz) = d267cf762530824b69763fbed4241d2b7a3a786a7de7ea314d3bb73727681ca5c46e220537eabbf5a737a6fd2f9f33853847705f62dbbb26f69b4269328a37b2
+SHA512 (chromium-151.0.7922.173-clean.tar.xz) = facaae2b8dbb69aef39ef105bb8524161ccbf42f64b7977be566ee91dba7e2698e79d57986ec3f3afe668dd079a08c8ce64808d3129a85f14e806bde12723165

                 reply	other threads:[~2026-09-04 17:42 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=178854377732.1.17199232464259785700.rpms-cef-6488ba1c5bc1@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