CVE Vulnerabilities

CVE-2025-43421

Out-of-bounds Read

Published: Nov 04, 2025 | Modified: Dec 17, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
8.8 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

Multiple issues were addressed by disabling array allocation sinking. This issue is fixed in iOS 26.1 and iPadOS 26.1, macOS Tahoe 26.1, visionOS 26.1, Safari 26.1. Processing maliciously crafted web content may lead to an unexpected process crash.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Safari Apple * 26.1 (excluding)
Ipados Apple * 26.1 (excluding)
Iphone_os Apple * 26.1 (excluding)
Visionos Apple * 26.1 (excluding)
Red Hat Enterprise Linux 7 Extended Lifecycle Support RedHat webkitgtk4-0:2.50.3-2.el7_9 *
Red Hat Enterprise Linux 8 RedHat webkit2gtk3-0:2.50.3-1.el8_10 *
Red Hat Enterprise Linux 8.2 Advanced Update Support RedHat webkit2gtk3-0:2.50.3-2.el8_2 *
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support RedHat webkit2gtk3-0:2.50.3-2.el8_4 *
Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On RedHat webkit2gtk3-0:2.50.3-2.el8_4 *
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support RedHat webkit2gtk3-0:2.50.3-2.el8_6 *
Red Hat Enterprise Linux 8.6 Telecommunications Update Service RedHat webkit2gtk3-0:2.50.3-2.el8_6 *
Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions RedHat webkit2gtk3-0:2.50.3-2.el8_6 *
Red Hat Enterprise Linux 8.8 Telecommunications Update Service RedHat webkit2gtk3-0:2.50.3-2.el8_8 *
Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions RedHat webkit2gtk3-0:2.50.3-2.el8_8 *
Red Hat Enterprise Linux 9 RedHat webkit2gtk3-0:2.50.3-1.el9_7 *
Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions RedHat webkit2gtk3-0:2.50.3-1.el9_0 *
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions RedHat webkit2gtk3-0:2.50.3-1.el9_2 *
Red Hat Enterprise Linux 9.4 Extended Update Support RedHat webkit2gtk3-0:2.50.3-1.el9_4 *
Red Hat Enterprise Linux 9.6 Extended Update Support RedHat webkit2gtk3-0:2.50.3-1.el9_6 *
Qtwebkit-opensource-src Ubuntu esm-apps/bionic *
Qtwebkit-opensource-src Ubuntu esm-apps/focal *
Qtwebkit-opensource-src Ubuntu esm-apps/jammy *
Qtwebkit-opensource-src Ubuntu esm-apps/noble *
Qtwebkit-opensource-src Ubuntu esm-infra/xenial *
Qtwebkit-opensource-src Ubuntu jammy *
Qtwebkit-opensource-src Ubuntu noble *
Qtwebkit-source Ubuntu esm-apps/bionic *
Qtwebkit-source Ubuntu esm-apps/xenial *
Webkit2gtk Ubuntu devel *
Webkit2gtk Ubuntu esm-infra/bionic *
Webkit2gtk Ubuntu esm-infra/focal *
Webkit2gtk Ubuntu esm-infra/xenial *
Webkit2gtk Ubuntu upstream *
Webkitgtk Ubuntu esm-apps/bionic *
Webkitgtk Ubuntu esm-apps/xenial *
Wpewebkit Ubuntu esm-apps/focal *
Wpewebkit Ubuntu esm-apps/jammy *
Wpewebkit Ubuntu jammy *
Wpewebkit Ubuntu upstream *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References