CVE Vulnerabilities

CVE-2025-43356

Exposure of Sensitive Information to an Unauthorized Actor

Published: Sep 15, 2025 | Modified: Nov 04, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
6.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

The issue was addressed with improved handling of caches. This issue is fixed in Safari 26, tvOS 26, watchOS 26, iOS 26 and iPadOS 26, visionOS 26, iOS 18.7 and iPadOS 18.7. A website may be able to access sensor information without user consent.

Weakness

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

Affected Software

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

Extended Description

There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:

Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:

Information exposures can occur in different ways:

It is common practice to describe any loss of confidentiality as an “information exposure,” but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information.

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References