chromium-browser: angle: Out of bounds write in ANGLE

An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=499129768...

webkitgtk: webkitgtk: Maliciously crafted web content may cause unexpected process crash

A flaw was found in WebKitGTK. Processing maliciously crafted web content can trigger an out-of-bounds write due to improper input validation, resulting in an unexpected process crash...

chromium-browser: angle: ANGLE Out-of-Bounds Write Vulnerability

A flaw was found in chromium-browser. An out-of-bounds write vulnerability exists within the ANGLE graphics component, allowing a remote attacker to trigger out-of-bounds memory access by providing a specially crafted HTML page. This allows an attacker to potentially manipulate memory contents. T...

webkitgtk: webkitgtk: Maliciously crafted web content may cause unexpected process crash

A flaw was found in WebKitGTK. Processing maliciously crafted web content can trigger an out-of-bounds write due to improper memory handling, resulting in an unexpected process crash...

chromium-browser: angle: Chromium: Sandbox escape via out-of-bounds write in ANGLE

A flaw was found in ANGLE, a component of Chromium. A remote attacker who has compromised the renderer process could exploit an out-of-bounds write vulnerability by crafting a malicious HTML page. This could potentially allow the attacker to escape the sandbox, leading to further system compromis...

chromium-browser: angle: Out of bounds read and write in Angle

An out of bounds read and write flaw was found in the Angle component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=498746519...

chromium-browser: angle: Out of bounds write in ANGLE

An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=500080303...

chromium-browser: angle: chromium-browser: Out of bounds write in ANGLE

An out of bounds write flaw was found in the ANGLE component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=513920258...

chromium-browser: angle: ANGLE in Google Chrome: Arbitrary code execution via out-of-bounds write

A flaw was found in ANGLE in Google Chrome. A remote attacker could exploit an out-of-bounds write vulnerability by enticing a user to visit a specially crafted HTML page. This could allow the attacker to execute arbitrary code outside of the browser's security sandbox, leading to a compromise of...

chromium-browser: angle: Chromium: Remote code execution via out-of-bounds write in ANGLE

A flaw was found in ANGLE, a component of Chromium. A remote attacker could exploit an out-of-bounds write vulnerability by enticing a user to visit a specially crafted HTML page. This could lead to arbitrary code execution outside of the sandbox, allowing the attacker to gain control over the...

chromium-browser: angle: Out of bounds read and write in ANGLE

An out of bounds read and write flaw was found in the ANGLE component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=511719039...

chromium-browser: skia: chromium-browser: skia: Out of bounds write in Skia

An out of bounds write flaw was found in the Skia component of the Chromium browser. Upstream bugs: https://code.google.com/p/chromium/issues/detail?id=538332338...

CVE-2026-102123

A path traversal vulnerability exists in the Kiteworks appliance setup interface because the system fails to confine user-supplied file paths to their intended directory. An unauthenticated attacker with network access to the interface could write files to any location writable by the service acc...

EUVD-2026-90295

A Kiteworks appliance setup interface did not confine a user-supplied file path to its intended directory, which could allow an unauthenticated attacker to write a file to any location writable by the affected service account, potentially compromising the integrity of the appliance or rendering i...

CVE-2026-102123 Kiteworks Core Path Traversal

A Kiteworks appliance setup interface did not confine a user-supplied file path to its intended directory, which could allow an unauthenticated attacker to write a file to any location writable by the affected service account, potentially compromising the integrity of the appliance or rendering i...

CVE-2026-102123 Kiteworks Core Path Traversal

A Kiteworks appliance setup interface did not confine a user-supplied file path to its intended directory, which could allow an unauthenticated attacker to write a file to any location writable by the affected service account, potentially compromising the integrity of the appliance or rendering i...

CVE-2026-102133

An optional, separately licensed repository-connector feature in Kiteworks Core is vulnerable to command injection because it fails to neutralize special characters in user-supplied paths before passing them to an external command. An authenticated system administrator can inject commands to writ...

CVE-2026-102133 Kiteworks Core Arbitrary File Write through Command Injection

An optional, separately licensed repository-connector feature in Kiteworks Core did not neutralize special characters in a user-supplied path before passing it to an external command. An authenticated system administrator could inject additional commands and write arbitrary content to files owned...

CVE-2026-102133 Kiteworks Core Arbitrary File Write through Command Injection

An optional, separately licensed repository-connector feature in Kiteworks Core did not neutralize special characters in a user-supplied path before passing it to an external command. An authenticated system administrator could inject additional commands and write arbitrary content to files owned...

EUVD-2026-90273

Two Kiteworks Core cluster-management operations did not validate file paths supplied to them, so an attacker holding root on one node of a cluster could write files as root onto another node and cause them to be executed there. Exploitation requires backend root access on a cluster node and a...