diff --git a/chromium-89.0.4389.82-rhel8-force-disable-use_gnome_keyring.patch b/chromium-89.0.4389.82-rhel8-force-disable-use_gnome_keyring.patch
new file mode 100644
index 00000000..f5f485a7
--- /dev/null
+++ b/chromium-89.0.4389.82-rhel8-force-disable-use_gnome_keyring.patch
@@ -0,0 +1,10 @@
+diff -up chromium-76.0.3809.132/components/os_crypt/features.gni.rhel8 chromium-76.0.3809.132/components/os_crypt/features.gni
+--- chromium-76.0.3809.132/components/os_crypt/features.gni.rhel8	2019-09-06 17:08:01.242314126 -0400
++++ chromium-76.0.3809.132/components/os_crypt/features.gni	2019-09-06 17:08:10.139134707 -0400
+@@ -7,5 +7,5 @@ import("//build/config/ui.gni")
+ declare_args() {
+   # Whether to use libgnome-keyring (deprecated by libsecret).
+   # See http://crbug.com/466975 and http://crbug.com/355223.
+-  use_gnome_keyring = (is_linux || is_chromeos_lacros) && use_glib
++  use_gnome_keyring = false
+ }
diff --git a/chromium.spec b/chromium.spec
index 215fbe0c..8ba094e5 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -330,7 +330,7 @@ Patch203:	chromium-86.0.4240.75-vaapi-i686-fpermissive.patch
 Patch205:	chromium-86.0.4240.75-fix-vaapi-on-intel.patch
 
 # Apply these patches to work around EPEL8 issues
-Patch300:	chromium-88.0.4324.96-rhel8-force-disable-use_gnome_keyring.patch
+Patch300:	chromium-89.0.4389.82-rhel8-force-disable-use_gnome_keyring.patch
 
 # And fixes for new compilers
 Patch400:       %{name}-gcc11.patch