CVE Vulnerabilities

CVE-2026-28859

Out-of-bounds Read

Published: Mar 25, 2026 | Modified: Jun 30, 2026
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
root.io logo minimus.io logo echo.ai logo

The issue was addressed with improved memory handling. This issue is fixed in Safari 26.4, iOS 26.4 and iPadOS 26.4, macOS Tahoe 26.4, tvOS 26.4, visionOS 26.4, watchOS 26.4. A malicious website may be able to process restricted web content outside the sandbox.

Weakness

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

Affected Software

NameVendorStart VersionEnd Version
SafariApple*26.4 (excluding)
IpadosApple*26.4 (excluding)
Iphone_osApple*26.4 (excluding)
MacosApple*26.4 (excluding)
TvosApple*26.4 (excluding)
VisionosApple*26.4 (excluding)
WatchosApple*26.4 (excluding)
Red Hat Enterprise Linux 7 Extended Lifecycle SupportRedHatwebkitgtk4-0:2.52.3-1.el7_9*
Red Hat Enterprise Linux 8RedHatwebkit2gtk3-0:2.52.3-1.el8_10*
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update SupportRedHatwebkit2gtk3-0:2.52.3-1.el8_4*
Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-OnRedHatwebkit2gtk3-0:2.52.3-1.el8_4*
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update SupportRedHatwebkit2gtk3-0:2.52.3-1.el8_6*
Red Hat Enterprise Linux 8.6 Telecommunications Update ServiceRedHatwebkit2gtk3-0:2.52.3-1.el8_6*
Red Hat Enterprise Linux 8.6 Update Services for SAP SolutionsRedHatwebkit2gtk3-0:2.52.3-1.el8_6*
Red Hat Enterprise Linux 8.8 Telecommunications Update ServiceRedHatwebkit2gtk3-0:2.52.3-1.el8_8*
Red Hat Enterprise Linux 8.8 Update Services for SAP SolutionsRedHatwebkit2gtk3-0:2.52.3-1.el8_8*
Red Hat Enterprise Linux 9RedHatwebkit2gtk3-0:2.52.3-1.el9_8*
Red Hat Enterprise Linux 9RedHatwebkit2gtk3-0:2.52.3-0.el9_7.1*
Red Hat Enterprise Linux 9.0 Update Services for SAP SolutionsRedHatwebkit2gtk3-0:2.52.3-1.el9_0*
Red Hat Enterprise Linux 9.2 Update Services for SAP SolutionsRedHatwebkit2gtk3-0:2.52.3-1.el9_2*
Red Hat Enterprise Linux 9.4 Extended Update SupportRedHatwebkit2gtk3-0:2.52.3-1.el9_4*
Red Hat Enterprise Linux 9.6 Extended Update SupportRedHatwebkit2gtk3-0:2.52.3-1.el9_6*
Qtwebkit-opensource-srcUbuntuesm-apps/bionic*
Qtwebkit-opensource-srcUbuntuesm-apps/focal*
Qtwebkit-opensource-srcUbuntuesm-apps/jammy*
Qtwebkit-opensource-srcUbuntuesm-apps/noble*
Qtwebkit-opensource-srcUbuntuesm-infra-legacy/xenial*
Qtwebkit-opensource-srcUbuntuesm-infra/xenial*
Qtwebkit-opensource-srcUbuntujammy*
Qtwebkit-opensource-srcUbuntunoble*
Qtwebkit-sourceUbuntuesm-apps-legacy/xenial*
Qtwebkit-sourceUbuntuesm-apps/bionic*
Qtwebkit-sourceUbuntuesm-apps/xenial*
Webkit2gtkUbuntudevel*
Webkit2gtkUbuntuesm-infra-legacy/xenial*
Webkit2gtkUbuntuesm-infra/bionic*
Webkit2gtkUbuntuesm-infra/focal*
Webkit2gtkUbuntuesm-infra/xenial*
Webkit2gtkUbuntujammy*
Webkit2gtkUbuntunoble*
Webkit2gtkUbuntuquesting*
Webkit2gtkUbunturesolute*
Webkit2gtkUbuntuupstream*
WebkitgtkUbuntuesm-apps-legacy/xenial*
WebkitgtkUbuntuesm-apps/bionic*
WebkitgtkUbuntuesm-apps/xenial*
WpewebkitUbuntuesm-apps/focal*
WpewebkitUbuntuesm-apps/jammy*
WpewebkitUbuntujammy*

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