1 day 19 hours ago
FEDORA-2026-9d3dc7f75e
Packages in this update:
Update description:
Valkey 9.0.8 - Released Wed 18 November 2026
Upgrade urgency SECURITY: This release includes security fixes we recommend you apply as soon as possible.
Security Fixes
- CVE-2026-130822: Fix a use-after-free crash in client eviction when maxmemory-clients is enabled by @nadav-levanoni (#5435)
Bug Fixes
See https://github.com/valkey-io/valkey/blob/9.0.8/00-RELEASENOTES
1 day 20 hours ago
FEDORA-EPEL-2026-e73d35f642
Packages in this update:
Update description:
WordPress 7.1.5 Release
Security updates included in this release
- A malformed regular expression that broadened JSON media type matching, fixed as a hardening measure, reported by Mo Jangda of the WordPress Security Team.
- A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.
- A reflected XSS in the legacy media library popup, reported by Anthropic.
- An XSS in wp_interactivity_data_wp_context() via the store namespace, reported by Juliette Reinders Folmer.
- SQL injection in WP_Meta_Query via nested relation values, reported by Christiaan Swiers.
- Unauthenticated information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.
- Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.
- SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.
- Contributor+ XSS via scripts in oEmbed provider responses, reported by vvh1te3zz.
- Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).
- Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
- Editor+ information disclosure via post and template author assignment in the REST API, reported by Jarda Snajdr of the WordPress Security Team.
- Administrator stored XSS via Customizer previews, reported by Weston Ruter of the WordPress Security Team.
- Author+ authorization bypass via comment editing in the admin, reported by Jesse McNeil.
- Subscriber+ information disclosure via XML-RPC wp.getComments, reported by Jaewook Lee (grze0).
- A hardening change that removes the block editor’s Imgur embed variation, whose server-side provider is already gone, reported by Zhengyu Liu, Jingcheng Yang, and Gavin Zhong.
- Contributor+ stored XSS in the Comment Date block via its date format, reported by Weston Ruter and Jeremy Felt of the WordPress Security Team.
- Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
- XSS in the block editor via Openverse image metadata, reported by Shu Takahashi of Velcore Consulting Inc.
- Contributor+ stored XSS in the block editor via media filenames when converting a media block to a File block, reported by CryptoFox.
1 day 20 hours ago
FEDORA-EPEL-2026-6433758199
Packages in this update:
Update description:
WordPress 6.9.12 Release
Security updates included in this release
- A malformed regular expression that broadened JSON media type matching, fixed as a hardening measure, reported by Mo Jangda of the WordPress Security Team.
- A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.
- A reflected XSS in the legacy media library popup, reported by Anthropic.
- An XSS in wp_interactivity_data_wp_context() via the store namespace, reported by Juliette Reinders Folmer.
- SQL injection in WP_Meta_Query via nested relation values, reported by Christiaan Swiers.
- Unauthenticated information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.
- Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.
- SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.
- Contributor+ XSS via scripts in oEmbed provider responses, reported by vvh1te3zz.
- Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).
- Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
- Editor+ information disclosure via post and template author assignment in the REST API, reported by Jarda Snajdr of the WordPress Security Team.
- Administrator stored XSS via Customizer previews, reported by Weston Ruter of the WordPress Security Team.
- Author+ authorization bypass via comment editing in the admin, reported by Jesse McNeil.
- Subscriber+ information disclosure via XML-RPC wp.getComments, reported by Jaewook Lee (grze0).
- A hardening change that removes the block editor’s Imgur embed variation, whose server-side provider is already gone, reported by Zhengyu Liu, Jingcheng Yang, and Gavin Zhong.
- Contributor+ stored XSS in the Comment Date block via its date format, reported by Weston Ruter and Jeremy Felt of the WordPress Security Team.
- Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
- XSS in the block editor via Openverse image metadata, reported by Shu Takahashi of Velcore Consulting Inc.
- Contributor+ stored XSS in the block editor via media filenames when converting a media block to a File block, reported by CryptoFox.
1 day 20 hours ago
FEDORA-2026-afd75b2de7
Packages in this update:
Update description:
WordPress 7.1.5 Release
Security updates included in this release
- A malformed regular expression that broadened JSON media type matching, fixed as a hardening measure, reported by Mo Jangda of the WordPress Security Team.
- A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.
- A reflected XSS in the legacy media library popup, reported by Anthropic.
- An XSS in wp_interactivity_data_wp_context() via the store namespace, reported by Juliette Reinders Folmer.
- SQL injection in WP_Meta_Query via nested relation values, reported by Christiaan Swiers.
- Unauthenticated information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.
- Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.
- SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.
- Contributor+ XSS via scripts in oEmbed provider responses, reported by vvh1te3zz.
- Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).
- Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
- Editor+ information disclosure via post and template author assignment in the REST API, reported by Jarda Snajdr of the WordPress Security Team.
- Administrator stored XSS via Customizer previews, reported by Weston Ruter of the WordPress Security Team.
- Author+ authorization bypass via comment editing in the admin, reported by Jesse McNeil.
- Subscriber+ information disclosure via XML-RPC wp.getComments, reported by Jaewook Lee (grze0).
- A hardening change that removes the block editor’s Imgur embed variation, whose server-side provider is already gone, reported by Zhengyu Liu, Jingcheng Yang, and Gavin Zhong.
- Contributor+ stored XSS in the Comment Date block via its date format, reported by Weston Ruter and Jeremy Felt of the WordPress Security Team.
- Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
- XSS in the block editor via Openverse image metadata, reported by Shu Takahashi of Velcore Consulting Inc.
- Contributor+ stored XSS in the block editor via media filenames when converting a media block to a File block, reported by CryptoFox.
1 day 20 hours ago
FEDORA-2026-86dbb8e4c9
Packages in this update:
Update description:
WordPress 6.9.12 Release
Security updates included in this release
- A malformed regular expression that broadened JSON media type matching, fixed as a hardening measure, reported by Mo Jangda of the WordPress Security Team.
- A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.
- A reflected XSS in the legacy media library popup, reported by Anthropic.
- An XSS in wp_interactivity_data_wp_context() via the store namespace, reported by Juliette Reinders Folmer.
- SQL injection in WP_Meta_Query via nested relation values, reported by Christiaan Swiers.
- Unauthenticated information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.
- Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.
- SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.
- Contributor+ XSS via scripts in oEmbed provider responses, reported by vvh1te3zz.
- Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).
- Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
- Editor+ information disclosure via post and template author assignment in the REST API, reported by Jarda Snajdr of the WordPress Security Team.
- Administrator stored XSS via Customizer previews, reported by Weston Ruter of the WordPress Security Team.
- Author+ authorization bypass via comment editing in the admin, reported by Jesse McNeil.
- Subscriber+ information disclosure via XML-RPC wp.getComments, reported by Jaewook Lee (grze0).
- A hardening change that removes the block editor’s Imgur embed variation, whose server-side provider is already gone, reported by Zhengyu Liu, Jingcheng Yang, and Gavin Zhong.
- Contributor+ stored XSS in the Comment Date block via its date format, reported by Weston Ruter and Jeremy Felt of the WordPress Security Team.
- Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
- XSS in the block editor via Openverse image metadata, reported by Shu Takahashi of Velcore Consulting Inc.
- Contributor+ stored XSS in the block editor via media filenames when converting a media block to a File block, reported by CryptoFox.
1 day 20 hours ago
FEDORA-EPEL-2026-05d68a6733
Packages in this update:
Update description:
WordPress 7.1.5 Release
Security updates included in this release
- A malformed regular expression that broadened JSON media type matching, fixed as a hardening measure, reported by Mo Jangda of the WordPress Security Team.
- A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.
- A reflected XSS in the legacy media library popup, reported by Anthropic.
- An XSS in wp_interactivity_data_wp_context() via the store namespace, reported by Juliette Reinders Folmer.
- SQL injection in WP_Meta_Query via nested relation values, reported by Christiaan Swiers.
- Unauthenticated information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.
- Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.
- SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.
- Contributor+ XSS via scripts in oEmbed provider responses, reported by vvh1te3zz.
- Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).
- Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
- Editor+ information disclosure via post and template author assignment in the REST API, reported by Jarda Snajdr of the WordPress Security Team.
- Administrator stored XSS via Customizer previews, reported by Weston Ruter of the WordPress Security Team.
- Author+ authorization bypass via comment editing in the admin, reported by Jesse McNeil.
- Subscriber+ information disclosure via XML-RPC wp.getComments, reported by Jaewook Lee (grze0).
- A hardening change that removes the block editor’s Imgur embed variation, whose server-side provider is already gone, reported by Zhengyu Liu, Jingcheng Yang, and Gavin Zhong.
- Contributor+ stored XSS in the Comment Date block via its date format, reported by Weston Ruter and Jeremy Felt of the WordPress Security Team.
- Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
- XSS in the block editor via Openverse image metadata, reported by Shu Takahashi of Velcore Consulting Inc.
- Contributor+ stored XSS in the block editor via media filenames when converting a media block to a File block, reported by CryptoFox.
1 day 20 hours ago
FEDORA-2026-58d14c4259
Packages in this update:
Update description:
WordPress 6.9.12 Release
Security updates included in this release
- A malformed regular expression that broadened JSON media type matching, fixed as a hardening measure, reported by Mo Jangda of the WordPress Security Team.
- A multisite privilege escalation issue letting a site Administrator take over a Super Admin account via Customizer menu previews, reported by Yuval Miller.
- A reflected XSS in the legacy media library popup, reported by Anthropic.
- An XSS in wp_interactivity_data_wp_context() via the store namespace, reported by Juliette Reinders Folmer.
- SQL injection in WP_Meta_Query via nested relation values, reported by Christiaan Swiers.
- Unauthenticated information disclosure exposing private taxonomy terms via the REST API search endpoint, reported by Anthropic.
- Author+ information disclosure exposing user email addresses via the REST API comments endpoint, reported by Ben Bidner of the WordPress Security Team.
- SQL injection via the front page setting in Customizer changeset previews, reported by Rudy Faile of the WordPress Security Team.
- Contributor+ XSS via scripts in oEmbed provider responses, reported by vvh1te3zz.
- Unauthenticated stored XSS via shortcode attributes in comments, reported by Rafie Muhammad (Awesome Motive, Inc.).
- Unauthenticated denial of service via batched XML-RPC pingbacks, reported by Giovanni Cintolo.
- Editor+ information disclosure via post and template author assignment in the REST API, reported by Jarda Snajdr of the WordPress Security Team.
- Administrator stored XSS via Customizer previews, reported by Weston Ruter of the WordPress Security Team.
- Author+ authorization bypass via comment editing in the admin, reported by Jesse McNeil.
- Subscriber+ information disclosure via XML-RPC wp.getComments, reported by Jaewook Lee (grze0).
- A hardening change that removes the block editor’s Imgur embed variation, whose server-side provider is already gone, reported by Zhengyu Liu, Jingcheng Yang, and Gavin Zhong.
- Contributor+ stored XSS in the Comment Date block via its date format, reported by Weston Ruter and Jeremy Felt of the WordPress Security Team.
- Unauthenticated privilege escalation via Template Part block attributes that could lead to remote code execution, reported by Logan Homolka.
- XSS in the block editor via Openverse image metadata, reported by Shu Takahashi of Velcore Consulting Inc.
- Contributor+ stored XSS in the block editor via media filenames when converting a media block to a File block, reported by CryptoFox.
1 day 23 hours ago
Stephen Fewer and Tomer Schwartz discovered that nginx did not correctly
handle certain memory operations. A remote attacker could possibly use
this issue to cause a denial of service or execute arbitrary code. This
issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS,
Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS and Ubuntu 26.10.
(CVE-2026-123007)
Albert Ebb Metnir and Nir Ohfeld discovered that nginx did not correctly
handle certain reusable HTTP/2 connections. A remote attacker could possibly
use this issue to cause a denial of service or execute arbitrary code. This
issue only affected Ubuntu 16.04 LTS, Ubuntu 18.04 LTS, Ubuntu 20.04 LTS,
Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS and Ubuntu 26.10.
(CVE-2026-123633)
It was discovered that nginx did not correctly handle certain memory
operations. A remote attacker could possibly use this issue to cause a
denial of service or execute arbitrary code. (CVE-2026-113425)
It was discovered that nginx did not correctly handle resolving certain
names or addresses. A remote attacker could possibly use this issue to
cause a denial of service or execute arbitrary code. (CVE-2026-123634)
It was discovered that nginx did not correctly handle certain TLS
connections. A remote attacker could possibly use this issue to cause
a denial of service. This issue only affected Ubuntu 24.04 LTS,
Ubuntu 26.04 LTS and Ubuntu 26.10. (CVE-2026-118899)
It was discovered that nginx did not correctly handle certain client
certificate validations. A remote attacker could possibly use this issue
to bypass client certificate verifications. This issue only affected
Ubuntu 26.04 LTS and Ubuntu 26.10. (CVE-2026-120967)
It was discovered that nginx did not correctly handle certain reusable
HTTP/3 connections. A remote attacker could possibly use this issue to
cause a denial of service or execute arbitrary code. This issue only
affected Ubuntu 26.04 LTS and Ubuntu 26.10. (CVE-2026-121810)
Vivek Parikh discovered that nginx did not correctly handle parsing
certain ClientHello messages. A remote attacker could possibly use this
issue to leak sensitive information. This issue only affected
Ubuntu 26.04 LTS and Ubuntu 26.10. (CVE-2026-123640)
1 day 23 hours ago
1 day 23 hours ago
1 day 23 hours ago
1 day 23 hours ago
1 day 23 hours ago
1 day 23 hours ago
2 days 1 hour ago
2 days 1 hour ago
2 days 1 hour ago
2 days 6 hours ago
Albert Yang and Quang Luong discovered that the Compiler component of
OpenJDK 27 did not correctly handle certain inputs. A remote attacker could
possibly use this issue to cause a denial of service or execute arbitrary
code. (CVE-2026-114938)
It was discovered that the JGSS component of OpenJDK 27 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
or modify sensitive data. (CVE-2026-114939)
Nicholas Carlini discovered that the JSSE component of OpenJDK 27 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-114940)
It was discovered that the Compiler component of OpenJDK 27 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to read or modify sensitive data.
(CVE-2026-114941)
It was discovered that the Libraries component of OpenJDK 27 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to read or modify sensitive data.
(CVE-2026-114942)
It was discovered that the Hotspot component of OpenJDK 27 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to modify sensitive data. (CVE-2026-114943)
Alexander Dezhinov, Stanislav Dukhin, Nikita Kozlov, and Binbin Xu
discovered that the Core Java Libraries component of OpenJDK 27 did not
correctly authorize users. A remote attacker could possibly use this issue
to modify sensitive data. (CVE-2026-114944)
It was discovered that the Libraries component of OpenJDK 27 did not
correctly authorize users. A remote attacker could possibly use this issue
to modify sensitive data. (CVE-2026-114945)
It was discovered that the Compiler component of OpenJDK 27 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-114946)
Juraj Somorovsky, Maximilian Radoy, and Sven Hebrok discovered that the
JSSE component of OpenJDK 27 did not correctly authorize users. A remote
attacker could possibly use this issue to modify sensitive data.
(CVE-2026-114947)
Please see the following for more information:
https://openjdk.org/groups/vulnerability/advisories/2026-11-17
2 days 6 hours ago
Albert Yang and Quang Luong discovered that the Compiler component of
OpenJDK 25 did not correctly handle certain inputs. A remote attacker could
possibly use this issue to cause a denial of service or execute arbitrary
code. (CVE-2026-114938)
It was discovered that the JGSS component of OpenJDK 25 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
or modify sensitive data. (CVE-2026-114939)
Nicholas Carlini discovered that the JSSE component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-114940)
It was discovered that the Compiler component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to read or modify sensitive data.
(CVE-2026-114941)
It was discovered that the Libraries component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to read or modify sensitive data.
(CVE-2026-114942)
It was discovered that the Hotspot component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to modify sensitive data. (CVE-2026-114943)
Alexander Dezhinov, Stanislav Dukhin, Nikita Kozlov, and Binbin Xu
discovered that the Core Java Libraries component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to modify sensitive data. (CVE-2026-114944)
It was discovered that the Libraries component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to modify sensitive data. (CVE-2026-114945)
It was discovered that the Compiler component of OpenJDK 25 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-114946)
Juraj Somorovsky, Maximilian Radoy, and Sven Hebrok discovered that the
JSSE component of OpenJDK 25 did not correctly authorize users. A remote
attacker could possibly use this issue to modify sensitive data.
(CVE-2026-114947)
Please see the following for more information:
https://openjdk.org/groups/vulnerability/advisories/2026-11-17
2 days 6 hours ago
Albert Yang and Quang Luong discovered that the Compiler component of
OpenJDK 21 did not correctly handle certain inputs. A remote attacker could
possibly use this issue to cause a denial of service or execute arbitrary
code. (CVE-2026-114938)
It was discovered that the JGSS component of OpenJDK 21 did not correctly
authenticate users. A remote attacker could possibly use this issue to read
or modify sensitive data. (CVE-2026-114939)
Nicholas Carlini discovered that the JSSE component of OpenJDK 21 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-114940)
It was discovered that the Compiler component of OpenJDK 21 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to read or modify sensitive data.
(CVE-2026-114941)
It was discovered that the Libraries component of OpenJDK 21 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to read or modify sensitive data.
(CVE-2026-114942)
It was discovered that the Hotspot component of OpenJDK 21 did not
correctly authorize users. A remote attacker could possibly use this issue
to cause a denial of service or to modify sensitive data. (CVE-2026-114943)
Alexander Dezhinov, Stanislav Dukhin, Nikita Kozlov, and Binbin Xu
discovered that the Core Java Libraries component of OpenJDK 21 did not
correctly authorize users. A remote attacker could possibly use this issue
to modify sensitive data. (CVE-2026-114944)
It was discovered that the Libraries component of OpenJDK 21 did not
correctly authorize users. A remote attacker could possibly use this issue
to modify sensitive data. (CVE-2026-114945)
It was discovered that the Compiler component of OpenJDK 21 did not
correctly authorize users. A remote attacker could possibly use this issue
to read or modify sensitive data. (CVE-2026-114946)
Please see the following for more information:
https://openjdk.org/groups/vulnerability/advisories/2026-11-17