CRITICAL10.0CVE-2025-24201⚠ KEVApple Multiple Products WebKit Out-of-Bounds Write Vulnerability from 0, < 2.48.3-1~deb11u1
CRITICAL9.8CVE-2021-1871⚠ KEVApple iOS, iPadOS, and macOS WebKit Remote Code Execution Vulnerability from 0, < 2.32.0-2
CRITICAL9.8⚠ KEVApple iOS, iPadOS, and macOS WebKit Remote Code Execution Vulnerability
from 0, < 2.30.6-1
HIGH8.8⚠ KEVApple Multiple Products Use-After-Free WebKit Vulnerability
from 0, < 2.50.4-1~deb11u1
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.50.4-1~deb11u1
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.50.4-1~deb12u1
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.50.4-1~deb11u1
HIGH8.8⚠ KEVApple Multiple products Use-After-Free Vulnerability
from 0, < 2.42.1-1~deb11u1
HIGH8.8⚠ KEVApple Multiple Products Buffer Overflow Vulnerability
from 0, < 2.50.0-1
HIGH8.8⚠ KEVchromium - security update
from 0, < 2.48.5-1~deb11u1
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.46.4-1~deb11u1
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.46.4-1~deb11u1
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.46.4-1~deb12u1
HIGH8.8⚠ KEVApple Multiple Products WebKit Type Confusion Vulnerability
from 0, < 2.42.5-1~deb11u1
HIGH8.8⚠ KEVApple Multiple Products WebKit Memory Corruption Vulnerability
from 0, < 2.42.3-1~deb11u1
HIGH8.8⚠ KEVApple Multiple Products WebKit Code Execution Vulnerability
from 0, < 2.42.1-1~deb11u1
HIGH8.8⚠ KEVApple Multiple Products Unspecified Vulnerability
from 0, < 2.38.0-1~deb11u1
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.40.3-2~deb11u2
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.40.3-2~deb11u2
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.40.3-2~deb11u1
HIGH8.8⚠ KEVwebkit2gtk - security update
from 0, < 2.40.3-2~deb11u1
HIGH8.8⚠ KEVApple Multiple Products WebKit Memory Corruption Vulnerability
from 0, < 2.40.1-1~deb11u1
HIGH8.8⚠ KEVApple Multiple Products WebKit Use-After-Free Vulnerability
from 0, < 2.40.2-1~deb11u1
HIGH8.8⚠ KEVApple Multiple Products WebKit Use-After-Free Vulnerability
from 0, < 2.40.1-1~deb11u1
HIGH8.8⚠ KEVWebKitGTK Memory Corruption Vulnerability
from 0, < 2.26.0-1
HIGH8.8⚠ KEVwpewebkit - security update
from 0, < 2.38.5-1~deb11u1
HIGH8.8⚠ KEVwpewebkit - security update
from 0, < 2.38.5-1~deb10u1
HIGH8.8⚠ KEVwpewebkit - security update
from 0, < 2.38.5-1~deb11u1
HIGH8.8⚠ KEVApple iOS Type Confusion Vulnerability
from 0, < 2.38.3-1~deb11u1
HIGH8.8⚠ KEVwpewebkit - security update
from 0, < 2.36.7-1~deb11u1
HIGH8.8⚠ KEVwpewebkit - security update
from 0, < 2.36.7-1~deb11u1
HIGH8.8⚠ KEVwpewebkit - security update
from 0, < 2.36.7-1~deb10u1
HIGH8.8⚠ KEVchromium - security update
from 0, < 2.36.6-1~deb11u1
HIGH8.8⚠ KEVApple iOS, iPadOS, and macOS Webkit Use-After-Free Vulnerability
from 0, < 2.34.6-1~deb11u1
HIGH8.8⚠ KEVApple iOS WebKit Buffer Overflow Vulnerability
from 0, < 2.26.1-2
HIGH8.8⚠ KEVApple Multiple Products WebKit Memory Corruption Vulnerability
from 0, < 2.32.3-1
HIGH8.8⚠ KEVApple Multiple Products WebKit Integer Overflow Vulnerability
from 0, < 2.32.3-1
HIGH8.8⚠ KEVApple Multiple Products WebKit Storage Use-After-Free Vulnerability
from 0, < 2.30.1-1
HIGH8.8⚠ KEVApple iOS WebKit Use-After-Free Vulnerability
from 0, < 2.28.0-2
HIGH8.8⚠ KEVApple iOS WebKit Memory Corruption Vulnerability
from 0, < 2.26.1-2
HIGH8.8⚠ KEVApple iOS, iPadOS, macOS Use-After-Free Vulnerability
from 0, < 2.32.4-1~deb11u1
HIGH8.8⚠ KEVApple Multiple Products Type Confusion Vulnerability
from 0, < 2.30.6-1
HIGH8.8⚠ KEVApple Multiple Products Type Confusion Vulnerability
from 0, < 2.24.1-1
HIGH8.6⚠ KEVApple Multiple Products WebKit Sandbox Escape Vulnerability
from 0, < 2.42.0-1
HIGH7.8⚠ KEVApple Multiple Products Integer Overflow or Wraparound Vulnerability
from 0, < 2.34.4-1~deb11u1
MEDIUM6.5⚠ KEVwebkit2gtk - security update
from 0, < 2.42.3-1~deb11u1
MEDIUM6.5⚠ KEVwebkit2gtk - security update
from 0, < 2.42.3-1~deb11u1
MEDIUM6.5⚠ KEVwebkit2gtk - security update
from 0, < 2.40.2-1~deb11u1
MEDIUM6.5⚠ KEVwebkit2gtk - security update
from 0, < 2.40.2-1~deb11u1
MEDIUM6.3⚠ KEVApple Multiple Products Cross-Site Scripting (XSS) Vulnerability
from 0, < 2.46.4-1~deb11u1
CRITICAL10.0webkit2gtk - security update
from 0, < 2.28.3-2~deb10u1
CRITICAL10.0webkit2gtk - security update
from 0, < 2.28.3-1
CRITICAL9.8The issue was addressed with improved memory handling.
from 0, < 2.50.1-1~deb11u1
CRITICAL9.8A correctness issue was addressed with improved checks.
from 0, < 2.50.1-1~deb11u1
CRITICAL9.8The issue was addressed with improved memory handling.
from 0, < 2.48.3-1~deb11u1
CRITICAL9.8The issue was addressed with improved memory handling.
from 0, < 2.46.0-1
CRITICAL9.8A use-after-free issue was addressed with improved memory management.
from 0, < 2.42.1-1~deb11u1
CRITICAL9.8The issue was addressed with improved checks.
from 0, < 2.40.5-1~deb11u1
CRITICAL9.8A use after free issue was addressed with improved memory management.
from 0, < 2.28.4-1
CRITICAL9.8A logic issue was addressed with improved restrictions.
from 0, < 2.28.3-1
CRITICAL9.8webkit2gtk - security update
from 0, < 2.26.4-1~deb10u2
CRITICAL9.8webkit2gtk - security update
from 0, < 2.28.0-2
CRITICAL9.8The UIProcess subsystem in WebKit, as used in WebKitGTK through 2.23.90 and WebKitGTK+ through 2.22.6 and other products, does not prevent…
from 0, < 2.24.1-1
CRITICAL9.8WebKitGTK+ 2.20.3 has an off-by-one error, with a resultant out-of-bounds write, in the get_simple_globs functions in ThirdParty/xdgmime/sr…
from 0, < 2.20.4-1
CRITICAL9.8WTF/wtf/FastBitVector.h in WebKit, as distributed in Safari Technology Preview Release 46, allows remote attackers to cause a denial of ser…
from 0, < 2.22.0-2
CRITICAL9.8The UNIX IPC layer in WebKit, including WebKitGTK+ prior to 2.16.3, does not properly validate message size metadata, allowing a compromise…
from 0, < 2.16.3-2
CRITICAL9.6chromium - security update
from 0, < 2.44.3-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.44.1-1~deb11u1
HIGH8.8A flaw was found in WebKitGTK.
from 0, < 2.50.3-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.50.2-1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.50.2-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.50.0-1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.48.5-1~deb11u1
HIGH8.8webkit2gtk - security update
from 0, < 2.48.5-1~deb11u1
HIGH8.8webkit2gtk - security update
from 0, < 2.48.5-1~deb12u1
HIGH8.8webkit2gtk - security update
from 0, < 2.48.5-1~deb11u1
HIGH8.8The issue was addressed with improved checks.
from 0, < 2.48.0-1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.48.3-1~deb11u1
HIGH8.8A use-after-free issue was addressed with improved memory management.
from 0, < 2.42.1-1~deb11u1
HIGH8.8A privacy issue was addressed with improved handling of files.
from 0, < 2.46.6-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.46.5-1~deb11u1
HIGH8.8A type confusion issue was addressed with improved memory handling.
from 0, < 2.46.5-1~deb11u1
HIGH8.8The issue was addressed with improved bounds checks.
from 0, < 2.44.3-1
HIGH8.8An integer overflow was addressed with improved input validation.
from 0, < 2.44.2-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.44.2-1~deb11u1
HIGH8.8webkit2gtk - security update
from 0, < 2.44.2-1~deb11u1
HIGH8.8webkit2gtk - security update
from 0, < 2.44.2-1~deb11u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.44.1-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.42.5-1~deb11u1
HIGH8.8A correctness issue was addressed with improved checks.
from 0, < 2.38.0-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.42.1-1~deb11u1
HIGH8.8A logic issue was addressed with improved checks.
from 0, < 2.42.2-1~deb11u1
HIGH8.8A use-after-free vulnerability exists in the MediaRecorder API of Webkit WebKitGTK 2.40.5.
from 0, < 2.42.1-1~deb11u1
HIGH8.8The issue was addressed with improved checks.
from 0, < 2.42.1-1~deb11u1
HIGH8.8This issue was addressed with improved iframe sandbox enforcement.
from 0, < 2.40.5-1~deb11u1
HIGH8.8A use-after-free issue was addressed with improved memory management.
from 0, < 2.40.5-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.40.1-1~deb11u1
HIGH8.8A use-after-free issue was addressed with improved memory management.
from 0, < 2.40.1-1~deb11u1
HIGH8.8A logic issue was addressed with improved restrictions.
from 0, < 2.40.5-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.40.5-1~deb11u1
HIGH8.8The issue was addressed with improved checks.
from 0, < 2.40.5-1~deb11u1
HIGH8.8The issue was addressed with improved checks.
from 0, < 2.40.5-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.40.1-1~deb11u1
HIGH8.8The issue was addressed with improved checks.
from 0, < 2.40.5-1~deb11u1
HIGH8.8The issue was addressed with improved checks.
from 0, < 2.40.5-1~deb11u1
HIGH8.8A memory corruption issue was addressed with improved validation.
from 0, < 2.40.1-1~deb11u1
HIGH8.8A use-after-free vulnerability in WebCore::RenderLayer::updateDescendantDependentFlags in WebKitGTK before 2.36.8 allows attackers to execu…
from 0, < 2.38.0-1~deb11u1
HIGH8.8A use-after-free vulnerability in WebCore::RenderLayer::repaintBlockSelectionGaps in WebKitGTK before 2.36.8 allows attackers to execute co…
from 0, < 2.38.0-1~deb11u1
HIGH8.8A use-after-free vulnerability in WebCore::RenderLayer::setNextSibling in WebKitGTK before 2.36.8 allows attackers to execute code remotely.
from 0, < 2.38.0-1~deb11u1
HIGH8.8A use-after-free vulnerability in WebCore::RenderLayer::renderer in WebKitGTK before 2.36.8 allows attackers to execute code remotely.
from 0, < 2.38.0-1~deb11u1
HIGH8.8A use-after-free vulnerability in WebCore::RenderLayer::addChild in WebKitGTK before 2.36.8 allows attackers to execute code remotely.
from 0, < 2.38.0-1~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.38.4-2~deb11u1
HIGH8.8The issue was addressed with improved memory handling.
from 0, < 2.38.4-2~deb11u1
HIGH8.8webkit2gtk - security update
from 0, < 2.38.4-2~deb11u1
HIGH8.8webkit2gtk - security update
from 0, < 2.38.4-2~deb10u1
HIGH8.8A memory corruption issue was addressed with improved input validation.
from 0, < 2.38.3-1~deb11u1
HIGH8.8A memory corruption issue was addressed with improved state management.
from 0, < 2.38.3-1~deb11u1
HIGH8.8A memory consumption issue was addressed with improved memory handling.
from 0, < 2.38.2-1~deb11u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.38.3-1~deb11u1
HIGH8.8A memory corruption issue was addressed with improved state management.
from 0, < 2.38.0-1~deb11u1
HIGH8.8A type confusion issue was addressed with improved memory handling.
from 0, < 2.38.2-1~deb11u1
HIGH8.8An out-of-bounds write issue was addressed with improved bounds checking.
from 0, < 2.38.0-1~deb11u1
HIGH8.8A memory corruption issue was addressed with improved state management.
from 0, < 2.36.3-1~deb11u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.36.3-1~deb11u1
HIGH8.8A memory corruption issue was addressed with improved state management.
from 0, < 2.36.3-1~deb11u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.36.4-1~deb11u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.36.3-1~deb11u1
HIGH8.8A buffer overflow issue was addressed with improved memory handling.
from 0, < 2.36.0-3~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.36.6-1~deb10u1
HIGH8.8wpewebkit - security update
from 0, < 2.36.6-1~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.36.6-1~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.36.3-1~deb10u1
HIGH8.8wpewebkit - security update
from 0, < 2.36.3-1~deb11u1
HIGH8.8A logic issue was addressed with improved state management.
from 0, < 2.34.4-1~deb11u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.36.0-3~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.36.0-3~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.36.0-3~deb10u1
HIGH8.8wpewebkit - security update
from 0, < 2.38.0-1~deb10u1
HIGH8.8wpewebkit - security update
from 0, < 2.38.0-1~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.38.0-1~deb11u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.34.6-1~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.34.1-1~deb10u1
HIGH8.8wpewebkit - security update
from 0, < 2.34.1-1~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.32.4-1~deb10u1
HIGH8.8wpewebkit - security update
from 0, < 2.32.4-1~deb11u1
HIGH8.8A memory corruption issue was addressed with improved state management.
from 0, < 2.30.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.32.3-1
HIGH8.8This issue was addressed with improved checks.
from 0, < 2.32.3-1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.32.3-1
HIGH8.8A type confusion issue was addressed with improved state handling.
from 0, < 2.32.2-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.32.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.32.3-1
HIGH8.8An out-of-bounds read was addressed with improved bounds checking.
from 0, < 2.34.4-1~deb11u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.34.4-1~deb11u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.34.4-1~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.34.4-1~deb11u1
HIGH8.8wpewebkit - security update
from 0, < 2.34.4-1~deb10u1
HIGH8.8A buffer overflow issue was addressed with improved memory handling.
from 0, < 2.34.1-1~deb11u1
HIGH8.8A memory corruption vulnerability was addressed with improved locking.
from 0, < 2.34.1-1~deb11u1
HIGH8.8An exploitable use-after-free vulnerability exists in WebKitGTK browser version 2.30.3 x64.
from 0, < 2.30.6-1
HIGH8.8A use-after-free vulnerability exists in the way Webkit’s GraphicsContext handles certain events in WebKitGTK 2.30.4.
from 0, < 2.32.3-1
HIGH8.8A memory corruption issue was addressed with improved validation.
from 0, < 2.32.0-2
HIGH8.8webkit2gtk - security update
from 0, < 2.32.0-2
HIGH8.8webkit2gtk - security update
from 0, < 2.32.1-1~deb10u1
HIGH8.8webkit2gtk - security update
from 0, < 2.30.5-1
HIGH8.8webkit2gtk - security update
from 0, < 2.30.5-1~deb10u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.30.1-1
HIGH8.8An exploitable use-after-free vulnerability exists in WebKitGTK browser version 2.30.1 x64.
from 0, < 2.30.3-1
HIGH8.8webkit2gtk - security update
from 0, < 2.30.3-1
HIGH8.8webkit2gtk - security update
from 0, < 2.30.3-1~deb10u1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.26.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.3-1
HIGH8.8webkit2gtk - security update
from 0, < 2.26.3-1~deb10u1
HIGH8.8webkit2gtk - security update
from 0, < 2.26.3-1
HIGH8.8An out-of-bounds write issue was addressed with improved bounds checking.
from 0, < 2.30.3-1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.30.1-1
HIGH8.8A type confusion issue was addressed with improved memory handling.
from 0, < 2.30.1-1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.28.4-1
HIGH8.8A memory corruption issue was addressed with improved state management.
from 0, < 2.28.3-1
HIGH8.8A memory corruption issue was addressed with improved state management.
from 0, < 2.28.3-1
HIGH8.8A memory corruption issue was addressed with improved validation.
from 0, < 2.28.3-1
HIGH8.8A logic issue was addressed with improved restrictions.
from 0, < 2.28.3-1
HIGH8.8webkit2gtk - security update
from 0, < 2.28.1-1
HIGH8.8webkit2gtk - security update
from 0, < 2.26.4-1~deb10u3
HIGH8.8A type confusion issue was addressed with improved memory handling.
from 0, < 2.28.0-2
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.28.0-2
HIGH8.8A memory consumption issue was addressed with improved memory handling.
from 0, < 2.28.2-1
HIGH8.8A type confusion issue was addressed with improved memory handling.
from 0, < 2.28.0-2
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.28.0-2
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.0-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.2-1
HIGH8.8webkit2gtk - security update
from 0, < 2.26.2-1
HIGH8.8webkit2gtk - security update
from 0, < 2.26.2-1~deb10+1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.0-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.0-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.0-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.0-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.2-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.26.0-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.2-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.2-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.2-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.2-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.2-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.3-1
HIGH8.8webkit2gtk - security update
from 0, < 2.24.4-1
HIGH8.8webkit2gtk - security update
from 0, < 2.24.4-1~deb10u1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.2-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8A memory corruption issue was addressed with improved state management.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8A logic issue was addressed with improved validation.
from 0, < 2.24.1-1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.0-2
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.22.3-1
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.22.3-1
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.22.3-1
HIGH8.8A logic issue existed resulting in memory corruption.
from 0, < 2.22.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.5-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.3-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.1-1
HIGH8.8A memory corruption issue was addressed with improved validation.
from 0, < 2.22.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.1-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.0-2
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.4-1
HIGH8.8A memory consumption issue was addressed with improved memory handling.
from 0, < 2.22.0-2
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.0-2
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.0-2
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.0-2
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.0-2
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.22.0-2
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.22.0-2
HIGH8.8A memory corruption issue was addressed with improved state management.
from 0, < 2.22.0-2
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.22.0-2
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.22.0-2
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.22.0-2
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.22.0-2
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.0-2
HIGH8.8A type confusion issue was addressed with improved memory handling.
from 0, < 2.20.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.20.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.20.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.20.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.20.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.20.4-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.20.4-1
HIGH8.8A use after free issue was addressed with improved memory management.
from 0, < 2.22.0-2
HIGH8.8A memory corruption issue was addressed with improved validation.
from 0, < 2.22.0-2
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.22.4-1
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.22.4-1
HIGH8.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.22.5-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.0-2
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.5-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.5-1
HIGH8.8A type confusion issue was addressed with improved memory handling.
from 0, < 2.22.6-1
HIGH8.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.22.6-1
HIGH8.8In Safari before 11.1.2, iTunes before 12.8 for Windows, iOS before 11.4.1, tvOS before 11.4.1, iCloud for Windows before 7.6, multiple mem…
from 0, < 2.20.4-1
HIGH8.8In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, tvOS before 11.3, watchOS before 4.3, iTunes before 12.7.4 for Windo…
from 0, < 2.22.0-2
HIGH8.8In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, tvOS before 11.3, watchOS before 4.3, iTunes before 12.7.4 for Windo…
from 0, < 2.22.0-2
HIGH8.8In iOS before 11.3, Safari before 11.1, tvOS before 11.3, watchOS before 4.3, iTunes before 12.7.4 for Windows, an array indexing issue exi…
from 0, < 2.22.0-2
HIGH8.8In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, tvOS before 11.3, watchOS before 4.3, iTunes before 12.7.4 for Windo…
from 0, < 2.22.0-2
HIGH8.8In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, tvOS before 11.3, watchOS before 4.3, iTunes before 12.7.4 for Windo…
from 0, < 2.22.0-2
HIGH8.8In iOS before 11.3, Safari before 11.1, iCloud for Windows before 7.4, tvOS before 11.3, watchOS before 4.3, iTunes before 12.7.4 for Windo…
from 0, < 2.22.0-2
HIGH8.8WebCore/platform/graphics/texmap/TextureMapperLayer.cpp in WebKit, as used in WebKitGTK+ prior to version 2.20.2, is vulnerable to a use af…
from 0, < 2.20.2-1
HIGH8.8The getImageData function in the ImageBufferCairo class in WebCore/platform/graphics/cairo/ImageBufferCairo.cpp in WebKit, as used in WebKi…
from 0, < 2.20.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.1-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.2-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH8.8WebKit in Apple iOS before 9.3.3, Safari before 9.1.2, and tvOS before 9.2.2 allows remote attackers to execute arbitrary code or cause a d…
from 0, < 2.12.4-1
HIGH8.8WebKit in Apple iOS before 9.3.3, Safari before 9.1.2, and tvOS before 9.2.2 allows remote attackers to execute arbitrary code or cause a d…
from 0, < 2.12.4-1
HIGH8.1The issue was addressed with improved checks.
from 0, < 2.46.0-1
HIGH8.1A cross-origin issue existed with "iframe" elements.
from 0, < 2.22.0-2
HIGH8.1The issue was addressed by removing origin information.
from 0, < 2.22.0-2
HIGH8.1WebKitGTK and WPE WebKit prior to version 2.24.1 are vulnerable to address bar spoofing upon certain JavaScript redirections.
from 0, < 2.24.1-1
HIGH8.1An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH8.0The issue was addressed with improved checks.
from 0, < 2.50.0-1
HIGH8.0webkit2gtk - security update
from 0, < 2.48.3-1~deb12u1
HIGH8.0webkit2gtk - security update
from 0, < 2.48.3-1~deb11u1
HIGH8.0webkit2gtk - security update
from 0, < 2.32.3-1~deb10u1
HIGH8.0webkit2gtk - security update
from 0, < 2.32.3-1
HIGH7.8This issue was addressed with improved handling of floats.
from 0, < 2.48.3-1~deb11u1
HIGH7.8webkit2gtk - security update
from 0, < 2.46.0-2~deb12u1
HIGH7.8webkit2gtk - security update
from 0, < 2.46.0-1
HIGH7.8Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.32.4-1~deb11u1
HIGH7.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.32.4-1~deb11u1
HIGH7.8A memory corruption issue was addressed with improved memory handling.
from 0, < 2.34.1-1~deb11u1
HIGH7.8A type confusion issue was addressed with improved memory handling.
from 0, < 2.34.4-1~deb11u1
HIGH7.8webkit2gtk - security update
from 0, < 2.30.6-1~deb10u1
HIGH7.8webkit2gtk - security update
from 0, < 2.30.6-1
HIGH7.8A logic issue was addressed with improved validation.
from 0, < 2.26.4-1
HIGH7.8webkit2gtk - security update
from 0, < 2.28.4-1
HIGH7.8webkit2gtk - security update
from 0, < 2.28.4-1~deb10u1
HIGH7.8An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH7.5The issue was addressed with improved memory handling.
from 0, < 2.50.6-1~deb11u1
HIGH7.5webkit2gtk - security update
from 0, < 2.50.2-1~deb12u1
HIGH7.5webkit2gtk - security update
from 0, < 2.50.2-1~deb11u1
HIGH7.5webkit2gtk - security update
from 0, < 2.50.2-1~deb11u1
HIGH7.5This issue was addressed through improved state management.
from 0, < 2.48.5-1~deb11u1
HIGH7.5webkit2gtk - security update
from 0, < 2.48.1-2~deb12u1
HIGH7.5webkit2gtk - security update
from 0, < 2.48.3-1~deb11u1
HIGH7.5The issue was addressed with improved memory handling.
from 0, < 2.46.5-1~deb11u1
HIGH7.5webkit2gtk - security update
from 0, < 2.46.5-1~deb12u1
HIGH7.5webkit2gtk - security update
from 0, < 2.46.5-1~deb11u1
HIGH7.5webkit2gtk - security update
from 0, < 2.46.5-1~deb11u1
HIGH7.5This issue was addressed with improved redaction of sensitive information.
from 0, < 2.42.1-1~deb11u1
HIGH7.5The issue was addressed with improved checks.
from 0, < 2.40.5-1~deb11u1
HIGH7.5In WebKitGTK through 2.36.0 (and WPE WebKit), there is a heap-based buffer overflow in WebCore::TextureMapperLayer::setContentsLayer in Web…
from 0, < 2.36.3-1~deb11u1
HIGH7.5A race condition was addressed with improved state handling.
from 0, < 2.34.4-1~deb11u1
HIGH7.5An issue was discovered in certain Apple products.
from 0, < 2.20.1-1
HIGH7.5WebCore/platform/network/soup/SocketStreamHandleImplSoup.cpp in the libsoup network backend of WebKit, as used in WebKitGTK+ versions 2.20.…
from 0, < 2.20.2-1
HIGH7.5webkitFaviconDatabaseSetIconForPageURL and webkitFaviconDatabaseSetIconURLForPageURL in UIProcess/API/glib/WebKitFaviconDatabase.cpp in Web…
from 0, < 2.20.3-1
HIGH7.5An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
HIGH7.5An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH7.5An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
HIGH7.5An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
HIGH7.5WebKit in Apple iOS before 9.3.3, Safari before 9.1.2, and tvOS before 9.2.2 mishandles the location variable, which allows remote attacker…
from 0, < 2.12.4-1
HIGH7.4webkit2gtk - security update
from 0, < 2.50.3-1~deb12u1
HIGH7.4webkit2gtk - security update
from 0, < 2.50.3-1~deb11u1
HIGH7.4webkit2gtk - security update
from 0, < 2.50.3-1~deb11u1
HIGH7.4An information leakage issue was addressed.
from 0, < 2.34.1-1~deb11u1
HIGH7.3Processing web content may lead to arbitrary code execution.
from 0, < 2.42.1-1~deb11u1
HIGH7.1An input validation issue was addressed with improved input validation.
from 0, < 2.28.3-1
HIGH7.1An input validation issue was addressed with improved input validation.
from 0, < 2.28.3-1
HIGH7.1A logic issue was addressed with improved restrictions.
from 0, < 2.28.3-1
HIGH7.1An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
HIGH7.1webkit2gtk - security update
from 0, < 2.42.1-1~deb11u1
HIGH7.1webkit2gtk - security update
from 0, < 2.42.1-1~deb11u1
HIGH7.0A buffer overflow issue was addressed with improved memory handling.
from 0, < 2.48.3-1~deb11u1
MEDIUM6.5The issue was addressed with improved memory handling.
from 0
MEDIUM6.5This issue was addressed through improved state management.
from 0
MEDIUM6.5The issue was addressed with improved memory handling.
from 0, < 2.50.6-1~deb11u1
MEDIUM6.5The issue was addressed with improved memory handling.
from 0, < 2.50.6-1~deb11u1
MEDIUM6.5A use-after-free issue was addressed with improved memory management.
from 0, < 2.50.6-1~deb11u1
MEDIUM6.5A use-after-free issue was addressed with improved memory management.
from 0, < 2.50.6-1~deb11u1
MEDIUM6.5This issue was addressed with improved checks.
from 0, < 2.50.2-1~deb11u1
MEDIUM6.5The issue was addressed with improved handling of caches.
from 0, < 2.50.1-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.50.1-1~deb12u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.50.1-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.50.1-1~deb11u1
MEDIUM6.5A use-after-free issue was addressed with improved memory management.
from 0, < 2.48.5-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.50.6-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.50.6-1~deb12u1
MEDIUM6.5The issue was addressed with improved memory handling.
from 0, < 2.50.5-1
MEDIUM6.5The issue was addressed with improved memory handling.
from 0, < 2.48.5-1~deb11u1
MEDIUM6.5The issue was addressed with improved checks.
from 0, < 2.48.3-1~deb11u1
MEDIUM6.5The issue was addressed with improved checks.
from 0, < 2.48.3-1~deb11u1
MEDIUM6.5A cookie management issue was addressed with improved state management.
from 0, < 2.48.3-1~deb11u1
MEDIUM6.5The issue was addressed with improved memory handling.
from 0, < 2.44.1-1~deb11u1
MEDIUM6.5This issue was addressed through improved state management.
from 0, < 2.46.6-1~deb11u1
MEDIUM6.5The issue was addressed with improved memory handling.
from 0, < 2.46.6-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.46.6-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.46.6-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.46.6-1~deb12u1
MEDIUM6.5The issue was addressed with improved checks.
from 0, < 2.46.5-1~deb11u1
MEDIUM6.5A cross-origin issue existed with "iframe" elements.
from 0, < 2.46.3-1~deb11u2
MEDIUM6.5webkit2gtk - security update
from 0, < 2.46.3-1~deb11u2
MEDIUM6.5webkit2gtk - security update
from 0, < 2.46.3-1~deb11u2
MEDIUM6.5An out-of-bounds access issue was addressed with improved bounds checking.
from 0, < 2.44.3-1~deb11u1
MEDIUM6.5A use-after-free issue was addressed with improved memory management.
from 0, < 2.44.3-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.44.3-1~deb12u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.44.3-1
MEDIUM6.5A logic issue was addressed with improved checks.
from 0, < 2.42.5-1~deb11u1
MEDIUM6.5The issue was addressed with improved memory handling.
from 0, < 2.44.1-1~deb11u1
MEDIUM6.5A logic issue was addressed with improved state management.
from 0, < 2.44.1-1~deb11u1
MEDIUM6.5An injection issue was addressed with improved validation.
from 0, < 2.44.1-1~deb11u1
MEDIUM6.5A logic issue was addressed with improved validation.
from 0, < 2.44.1-1~deb11u1
MEDIUM6.5The issue was addressed with improved UI handling.
from 0, < 2.44.1-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.42.5-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.42.5-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.42.2-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.42.2-1~deb11u1
MEDIUM6.5A logic issue was addressed with improved state management.
from 0, < 2.40.5-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.40.5-1~deb11u1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.40.5-1~deb11u1
MEDIUM6.5The issue was addressed by removing origin information.
from 0, < 2.40.1-1~deb11u1
MEDIUM6.5A logic issue was addressed with improved checks.
from 0, < 2.38.3-1~deb11u1
MEDIUM6.5wpewebkit - security update
from 0, < 2.38.3-1~deb11u1
MEDIUM6.5wpewebkit - security update
from 0, < 2.38.3-1~deb11u1
MEDIUM6.5wpewebkit - security update
from 0, < 2.38.3-1~deb10u1
MEDIUM6.5A correctness issue in the JIT was addressed with improved checks.
from 0, < 2.38.0-1~deb11u1
MEDIUM6.5The issue was addressed with improved UI handling.
from 0, < 2.36.6-1~deb11u1
MEDIUM6.5A cookie management issue was addressed with improved state management.
from 0, < 2.36.0-3~deb11u1
MEDIUM6.5A cross-origin issue in the IndexDB API was addressed with improved input validation.
from 0, < 2.34.4-1~deb11u1
MEDIUM6.5A logic issue was addressed with improved state management.
from 0, < 2.34.6-1~deb11u1
MEDIUM6.5wpewebkit - security update
from 0, < 2.40.1-1~deb11u1
MEDIUM6.5wpewebkit - security update
from 0, < 2.40.1-1~deb11u1
MEDIUM6.5wpewebkit - security update
from 0, < 2.38.6-0+deb10u1
MEDIUM6.5In WebKitGTK before 2.32.4, there is a use-after-free in WebCore::Frame::page, a different vulnerability than CVE-2021-30889.
from 0, < 2.34.1-1~deb11u1
MEDIUM6.5In WebKitGTK before 2.32.4, there is a use-after-free in WebCore::ContainerNode::firstChild, a different vulnerability than CVE-2021-30889.
from 0, < 2.32.4-1~deb11u1
MEDIUM6.5In WebKitGTK before 2.32.4, there is incorrect memory allocation in WebCore::ImageBufferCairoImageSurfaceBackend::create, leading to a segm…
from 0, < 2.34.1-1~deb11u1
MEDIUM6.5A logic issue was addressed with improved restrictions.
from 0, < 2.34.1-1~deb11u1
MEDIUM6.5A memory initialization issue was addressed with improved memory handling.
from 0, < 2.30.1-1
MEDIUM6.5wpewebkit - security update
from 0, < 2.34.3-1~deb10u1
MEDIUM6.5wpewebkit - security update
from 0, < 2.34.3-1~deb11u1
MEDIUM6.5This issue was addressed with improved iframe sandbox enforcement.
from 0, < 2.30.6-1
MEDIUM6.5A port redirection issue was addressed with additional port validation.
from 0, < 2.30.6-1
MEDIUM6.5This issue was addressed with improved iframe sandbox enforcement.
from 0, < 2.30.6-1
MEDIUM6.5An access issue existed in Content Security Policy.
from 0, < 2.28.4-1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.26.4-1
MEDIUM6.5webkit2gtk - security update
from 0, < 2.26.4-1~deb10u1
MEDIUM6.5Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.2-1
MEDIUM6.5An out-of-bounds read was addressed with improved input validation.
from 0, < 2.24.2-1
MEDIUM6.5Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
MEDIUM6.5A cross-origin issue existed with the fetch API.
from 0, < 2.24.1-1
MEDIUM6.5A validation issue was addressed with improved logic.
from 0, < 2.24.1-1
MEDIUM6.5Multiple memory corruption issues were addressed with improved input validation.
from 0, < 2.20.4-1
MEDIUM6.5Multiple memory corruption issues were addressed with improved input validation.
from 0, < 2.20.2-1
MEDIUM6.5A memory corruption issue was addressed with improved memory handling.
from 0, < 2.20.4-1
MEDIUM6.5WebCore/platform/network/soup/SocketStreamHandleImplSoup.cpp in the libsoup network backend of WebKit, as used in WebKitGTK+ prior to versi…
from 0, < 2.20.0-2
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.4-1
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
MEDIUM6.5An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
MEDIUM6.3Multiple memory corruption issues were addressed with improved memory handling.
from 0, < 2.24.1-1
MEDIUM6.2A logic issue was addressed with improved checks.
from 0, < 2.48.5-1~deb11u1
MEDIUM6.2The issue was addressed with improved memory handling.
from 0, < 2.48.5-1~deb11u1
MEDIUM6.1A permissions issue was addressed with additional restrictions.
from 0, < 2.48.3-1~deb11u1
MEDIUM6.1This issue was addressed with improved checks.
from 0, < 2.44.3-1~deb11u1
MEDIUM6.1The issue was addressed with improved UI handling.
from 0, < 2.36.6-1~deb11u1
MEDIUM6.1wpewebkit - security update
from 0, < 2.38.2-1~deb10u1
MEDIUM6.1wpewebkit - security update
from 0, < 2.38.2-1~deb11u1
MEDIUM6.1wpewebkit - security update
from 0, < 2.38.2-1~deb11u1
MEDIUM6.1wpewebkit - security update
from 0, < 2.34.6-1~deb11u1
MEDIUM6.1wpewebkit - security update
from 0, < 2.34.6-1~deb10u1
MEDIUM6.1A logic issue was addressed with improved state management.
from 0, < 2.32.3-1
MEDIUM6.1A logic issue was addressed with improved restrictions.
from 0, < 2.30.1-1
MEDIUM6.1An input validation issue was addressed with improved input validation.
from 0, < 2.30.1-1
MEDIUM6.1Description: A cross-origin issue with iframe elements was addressed with improved tracking of security origins.
from 0, < 2.32.3-1
MEDIUM6.1A logic issue was addressed with improved state management.
from 0, < 2.34.3-1~deb11u1
MEDIUM6.1This issue was addressed with improved iframe sandbox enforcement.
from 0, < 2.26.0-1
MEDIUM6.1A logic issue was addressed with improved state management.
from 0, < 2.28.4-1
MEDIUM6.1An input validation issue was addressed with improved input validation.
from 0, < 2.28.0-2
MEDIUM6.1A logic issue was addressed with improved state management.
from 0, < 2.26.4-1
MEDIUM6.1A logic issue was addressed with improved state management.
from 0, < 2.26.1-1
MEDIUM6.1A logic issue was addressed with improved state management.
from 0, < 2.26.0-1
MEDIUM6.1A logic issue was addressed with improved state management.
from 0, < 2.24.4-1
MEDIUM6.1A logic issue existed in the handling of document loads.
from 0, < 2.24.3-1
MEDIUM6.1A logic issue was addressed with improved state management.
from 0, < 2.24.4-1
MEDIUM6.1A logic issue was addressed with improved state management.
from 0, < 2.24.4-1
MEDIUM6.1A logic issue existed in the handling of synchronous page loads.
from 0, < 2.24.4-1
MEDIUM6.1webkit2gtk - security update
from 0, < 2.26.1-3~deb10u1
MEDIUM6.1webkit2gtk - security update
from 0, < 2.26.0-1
MEDIUM6.1A logic issue was addressed with improved validation.
from 0, < 2.24.1-1
MEDIUM6.1A cross-site scripting issue existed in Safari.
from 0, < 2.22.3-1
MEDIUM6.1A cross-site scripting issue existed in Safari.
from 0, < 2.22.0-2
MEDIUM6.1A logic issue was addressed with improved validation.
from 0, < 2.22.5-1
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.20.0-2
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.18.6-1
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
MEDIUM6.1A DOMParser XSS issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM6.1A DOMParser XSS issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.16.3-1
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.14.6-1
MEDIUM6.1An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM5.9A race condition was addressed with additional validation.
from 0, < 2.20.4-1
MEDIUM5.5This issue was addressed through improved state management.
from 0, < 2.50.6-1~deb11u1
MEDIUM5.5webkit2gtk - security update
from 0, < 2.48.3-1~deb11u1
MEDIUM5.5webkit2gtk - security update
from 0, < 2.48.3-1~deb11u1
MEDIUM5.5webkit2gtk - security update
from 0, < 2.48.0-1~deb12u1
MEDIUM5.5The issue was addressed with improved checks.
from 0, < 2.46.3-1~deb11u2
MEDIUM5.5An out-of-bounds read was addressed with improved bounds checking.
from 0, < 2.44.3-1~deb11u1
MEDIUM5.5An out-of-bounds read was addressed with improved bounds checking.
from 0, < 2.44.3-1~deb11u1
MEDIUM5.5The issue was addressed with improved checks.
from 0, < 2.44.2-1~deb11u1
MEDIUM5.5webkit2gtk - security update
from 0, < 2.42.4-1~deb11u1
MEDIUM5.5webkit2gtk - security update
from 0, < 2.42.4-1~deb11u1
MEDIUM5.5This issue was addressed with improved state management.
from 0, < 2.40.1-1~deb11u1
MEDIUM5.5A logic issue was addressed with improved state management.
from 0, < 2.38.3-1~deb11u1
MEDIUM5.5A logic issue was addressed with improved state management.
from 0, < 2.38.2-1~deb11u1
MEDIUM5.5An out-of-bounds read was addressed with improved input validation.
from 0, < 2.32.4-1~deb11u1
MEDIUM5.5A logic issue was addressed with improved restrictions.
from 0, < 2.32.0-2
MEDIUM5.5An issue was discovered in certain Apple products.
from 0, < 2.16.6-1
MEDIUM5.4A cross-origin issue in the Navigation API was addressed with improved input validation.
from 0
MEDIUM5.4The issue was addressed with improved checks.
from 0, < 2.46.3-1~deb11u2
MEDIUM5.4A logic issue was addressed with improved restrictions.
from 0, < 2.32.3-1
MEDIUM5.4WebKit in Apple iOS before 9.3.3 and Safari before 9.1.2 mishandles about: URLs, which allows remote attackers to bypass the Same Origin Po…
from 0, < 2.12.4-1
MEDIUM5.3This issue was addressed through improved state management.
from 0, < 2.50.6-1~deb11u1
MEDIUM5.3This issue was addressed through improved state management.
from 0, < 2.44.3-1~deb11u1
MEDIUM5.3An information disclosure issue was addressed by removing the vulnerable code.
from 0, < 2.38.0-1~deb11u1
MEDIUM5.3A logic issue was addressed with improved validation.
from 0, < 2.40.1-1~deb11u1
MEDIUM5.3BubblewrapLauncher.cpp in WebKitGTK and WPE WebKit before 2.34.1 allows a limited sandbox bypass that allows a sandboxed process to trick h…
from 0, < 2.34.1-1~deb11u1
MEDIUM5.3"Clear History and Website Data" did not clear the history.
from 0, < 2.24.0-1
MEDIUM5.3WebKitGTK and WPE WebKit prior to version 2.24.1 failed to properly apply configured HTTP proxy settings when downloading livestream video…
from 0, < 2.24.1-1
MEDIUM5.3The UNIX IPC layer in WebKit, including WebKitGTK+ prior to 2.16.3, does not properly validate certain message metadata, allowing a comprom…
from 0, < 2.16.3-2
MEDIUM5.3An issue was discovered in certain Apple products.
from 0, < 2.18.1-1
MEDIUM5.3An issue was discovered in certain Apple products.
from 0, < 2.16.3-2
MEDIUM4.7This issue was addressed with improved memory handling.
from 0, < 2.48.3-1~deb11u1
MEDIUM4.7wpewebkit - security update
from 0, < 2.38.4-2~deb11u1
MEDIUM4.7wpewebkit - security update
from 0, < 2.38.4-2~deb11u1
MEDIUM4.7The issue was resolved with additional restrictions on CSS compositing.
from 0, < 2.34.1-1~deb11u1
MEDIUM4.3A logic issue was addressed with improved checks.
from 0
MEDIUM4.3A logic issue was addressed with improved state management.
from 0
MEDIUM4.3The issue was addressed with improved memory handling.
from 0
MEDIUM4.3An authorization issue was addressed with improved state management.
from 0
MEDIUM4.3The issue was addressed with improved memory handling.
from 0
MEDIUM4.3The issue was addressed with improved memory handling.
from 0, < 2.50.6-1~deb11u1
MEDIUM4.3A memory initialization issue was addressed with improved memory handling.
from 0
MEDIUM4.3A type confusion issue was addressed with improved state handling.
from 0, < 2.50.4-1~deb11u1
MEDIUM4.3A use-after-free issue was addressed with improved memory management.
from 0, < 2.50.4-1~deb11u1
MEDIUM4.3The issue was addressed with improved memory handling.
from 0, < 2.50.4-1~deb11u1
MEDIUM4.3A buffer overflow issue was addressed with improved memory handling.
from 0, < 2.50.4-1~deb11u1
MEDIUM4.3This issue was addressed through improved state management.
from 0, < 2.50.3-1~deb11u1
MEDIUM4.3This issue was addressed with improved checks.
from 0, < 2.50.2-1~deb11u1
MEDIUM4.3The issue was addressed with improved memory handling.
from 0, < 2.50.2-1
MEDIUM4.3A use-after-free issue was addressed with improved memory management.
from 0, < 2.50.2-1
MEDIUM4.3A use-after-free issue was addressed with improved memory management.
from 0, < 2.50.2-1~deb11u1
MEDIUM4.3A use-after-free issue was addressed with improved memory management.
from 0, < 2.50.2-1~deb11u1
MEDIUM4.3This issue was addressed through improved state management.
from 0, < 2.50.2-1~deb11u1
MEDIUM4.3A buffer overflow was addressed with improved bounds checking.
from 0, < 2.50.2-1~deb11u1
MEDIUM4.3This issue was addressed through improved state management.
from 0, < 2.50.2-1~deb11u1
MEDIUM4.3The issue was addressed with improved memory handling.
from 0, < 2.50.2-1~deb11u1
MEDIUM4.3Multiple issues were addressed by disabling array allocation sinking.
from 0, < 2.50.3-1~deb11u1
MEDIUM4.3The issue was addressed with improved handling of caches.
from 0, < 2.50.2-1~deb11u1
MEDIUM4.3A use-after-free issue was addressed with improved memory management.
from 0, < 2.50.1-1~deb11u1
MEDIUM4.3The issue was addressed with improved UI.
from 0, < 2.48.5-1~deb11u1
MEDIUM4.3A type confusion issue was addressed with improved state handling.
from 0, < 2.48.3-1~deb11u1
MEDIUM4.3A use-after-free issue was addressed with improved memory management.
from 0, < 2.48.3-1~deb11u1
MEDIUM4.3The issue was addressed with improved memory handling.
from 0, < 2.48.3-1~deb11u1
MEDIUM4.3webkit2gtk - security update
from 0, < 2.46.3-1~deb11u2
MEDIUM4.3webkit2gtk - security update
from 0, < 2.46.3-1~deb12u1
MEDIUM4.3webkit2gtk - security update
from 0, < 2.44.3-1~deb11u1
MEDIUM4.3webkit2gtk - security update
from 0, < 2.44.3-1~deb11u1
MEDIUM4.3webkit2gtk - security update
from 0, < 2.44.1-1~deb11u1
MEDIUM4.3webkit2gtk - security update
from 0, < 2.44.1-1~deb11u1
MEDIUM4.3A spoofing issue existed in the handling of URLs.
from 0, < 2.38.4-2~deb11u1
MEDIUM4.3A spoofing issue existed in the handling of URLs.
from 0, < 2.38.4-2~deb11u1
MEDIUM4.3wpewebkit - security update
from 0, < 2.36.4-1~deb11u1
MEDIUM4.3wpewebkit - security update
from 0, < 2.36.4-1~deb10u1
MEDIUM4.3An out-of-bounds read was addressed with improved input validation.
from 0, < 2.28.4-1
MEDIUM4.3webkit2gtk - security update
from 0, < 2.28.2-2~deb10u1
MEDIUM4.3webkit2gtk - security update
from 0, < 2.28.0-2
MEDIUM4.3An issue existed in the drawing of web page elements.
from 0, < 2.26.0-1
MEDIUM4.3In Safari before 11.1.2, iTunes before 12.8 for Windows, iOS before 11.4.1, tvOS before 11.4.1, iCloud for Windows before 7.6, sound fetche…
from 0, < 2.20.4-1
MEDIUM4.3An issue was discovered in certain Apple products.
from 0, < 2.20.3-1
MEDIUM4.3An issue was discovered in certain Apple products.
from 0, < 2.14.3-1
MEDIUM4.0An out-of-bounds read was addressed with improved input validation.
from 0, < 2.48.5-1~deb11u1
LOW3.3"Clear History and Website Data" did not clear the history.
from 0, < 2.30.6-1
LOW3.1A race condition was addressed with improved state handling.
from 0, < 2.50.4-1~deb11u1
LOW3.1A race condition was addressed with additional validation.
from 0, < 2.28.0-2
—WebKit in Apple iOS before 9.2, Safari before 9.0.2, and tvOS before 9.1 allows remote attackers to execute arbitrary code or cause a denia…
from 0, < 2.10.5-1
—WebKit in Apple iOS before 9.2, Safari before 9.0.2, and tvOS before 9.1 allows remote attackers to execute arbitrary code or cause a denia…
from 0, < 2.10.5-1