CVE-2026-79034

A flaw was found in chromium-browser. A remote attacker, after compromising the renderer process, could exploit an information leak in Cross-Origin Resource Sharing CORS. This vulnerability allows the attacker to leak sensitive cross-origin data by tricking a user into visiting a specially crafte...

CVE-2026-79044

A flaw was found in WebAppInstalls in Google Chrome on Android. A remote attacker, after compromising the renderer process, could exploit missing authorization by using a specially crafted HTML page. This could allow the attacker to obtain sensitive information...

CVE-2026-79007

A flaw was found in Google Chrome's GPU component. This vulnerability, caused by an uninitialized resource, could allow a remote attacker to potentially read memory outside the browser's security sandbox. The attacker would first need to compromise the renderer process and then entice a user to...

CVE-2026-78986

A flaw was found in Chromium. A remote attacker, after compromising the renderer process, could exploit an uninitialized resource in the Graphics Processing Unit GPU by crafting a malicious HTML page. This could potentially lead to the disclosure of sensitive cross-origin data...

CVE-2026-78991

A flaw was found in WebProtect in Google Chrome. A race condition vulnerability allows a remote attacker, who has compromised the renderer process, to obtain sensitive information. This can be achieved by enticing a user to visit a specially crafted HTML page...

CVE-2026-78984

A flaw was found in the GPU component of Chromium. A remote attacker, who has already compromised the renderer process, could exploit an uninitialized resource vulnerability by crafting a malicious HTML page. This could potentially allow the attacker to read sensitive memory outside of the...

CVE-2026-78976

A flaw was found in Google Chrome. Improper input validation in the StorageAccessAPI could allow a remote attacker to bypass the web origin policy. This exploitation requires the attacker to first compromise the renderer process and then use a specially crafted HTML page. The successful bypass of...

CVE-2026-78941

A flaw was found in Google Chrome. A remote attacker, after compromising the renderer process, could exploit an information leak by using a specially crafted HTML page. This vulnerability allows the attacker to bypass site isolation, potentially leading to the disclosure of sensitive information...

CVE-2026-78903

A flaw was found in Google Chrome's Site Isolation feature. This vulnerability, caused by an incomplete cleanup process, could allow a remote attacker to bypass site isolation. To exploit this, the attacker must first compromise the browser's renderer process and then use a specially crafted HTML...

CVE-2026-79229

A flaw was found in ANGLE, a component within Chromium. This uninitialized resource vulnerability could allow a remote attacker, who has already compromised the renderer process, to read sensitive memory outside of the security sandbox. This exploitation can occur by tricking a user into visiting...

CVE-2026-79212

A flaw was found in Google Chrome. This vulnerability, stemming from missing authorization in the Passwords component, could allow a remote attacker to bypass the web origin policy. To exploit this, the attacker would first need to compromise the browser's renderer process and employ social...

CVE-2026-79186

A flaw was found in Google Chrome's Network component. Incorrect authorization could allow a remote attacker, who has already compromised the renderer process, to bypass site isolation. This bypass is achieved by presenting a specially crafted HTML page, potentially leading to unauthorized access...

CVE-2026-79132

A flaw was found in Google Chrome on Android. This improper input validation vulnerability allows a remote attacker, who has already compromised the renderer process, to potentially execute arbitrary code outside of the browser's security sandbox. This exploitation occurs when the attacker provid...

CVE-2026-79074

A flaw was found in Google Chrome's Network component. A remote attacker, after compromising the renderer process, could exploit this vulnerability by crafting a malicious HTML page. This could allow the attacker to obtain sensitive information, leading to an information leak...

CVE-2026-79292

A flaw was found in Chromecast within Google Chrome. An integer overflow vulnerability allows a remote attacker, who has already compromised the renderer process, to potentially execute arbitrary code outside of the sandbox environment. This exploitation can occur by tricking a user into visiting...

CVE-2026-79267

A flaw was found in chromium-browser. A race condition in the Workers component allowed a remote attacker, who had already compromised the renderer process, to bypass the web origin policy. This bypass was achieved by tricking a user into opening a specially crafted HTML page, potentially leading...

CVE-2026-79255

A flaw was found in WebRTC, a real-time communication component within Chromium. This improper input validation vulnerability allows a remote attacker, who has already compromised the renderer process, to bypass the web origin policy. This bypass can be achieved by tricking the user into visiting...

AZL-97830 CVE-2026-74747 affecting package kernel 6.6.157.1-1

In the Linux kernel, the following vulnerability has been resolved: ipvs: revalidate ihl to prevent out-of-bounds access While the outer IP header is already pulled into the skb head, we must be careful and revalidate the embedded headers after reading them from the skb frags to prevent...

UBUNTU-CVE-2026-74747

In the Linux kernel, the following vulnerability has been resolved: ipvs: revalidate ihl to prevent out-of-bounds access While the outer IP header is already pulled into the skb head, we must be careful and revalidate the embedded headers after reading them from the skb frags to prevent...

CVE-2026-74747 ipvs: revalidate ihl to prevent out-of-bounds access

In the Linux kernel, the following vulnerability has been resolved: ipvs: revalidate ihl to prevent out-of-bounds access While the outer IP header is already pulled into the skb head, we must be careful and revalidate the embedded headers after reading them from the skb frags to prevent...