CVE-2026-9112
published 2026-05-20CVE-2026-9112: Use after free in GPU in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted…
PriorityP354high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
0.40%
32.2th percentile
Use after free in GPU in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | < 148.0.7778.179 | 148.0.7778.179 | |
| chrome | >= 148.0.7778.179 < 148.0.7778.179 | 148.0.7778.179 | |
| chrome_desktop | — | — | |
| paloalto | prisma_browser | — | — |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vendor_redhat8.8HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Palo Alto
PAN-SA-2026-0008 Chromium: Monthly Vulnerability Update (June 2026)
vendor_paloalto·2026-06-10·CVSS 8.8
CVE-2026-8509 [HIGH] PAN-SA-2026-0008 Chromium: Monthly Vulnerability Update (June 2026)
PAN-SA-2026-0008 Chromium: Monthly Vulnerability Update (June 2026)
Palo Alto Networks incorporated the following Chromium security fixes into our products: https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0841193308.html https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html CVE Summary CVE-2026-8509 Heap buffer overflow in WebML CVE-2026-8510 Integer overflow in Skia CVE-2026-8511 Use after free in UI CVE-2026-8512 Use after free in FileSystem CVE-2026-8513 Use after free in Input CVE-2026-8514 Use after free in Aura CVE-2026-8515 Use after free
Red Hat
chromium-browser: Use after free in GPU
vendor_redhat·2026-05-19·CVSS 8.8
CVE-2026-9112 [HIGH] CWE-825 chromium-browser: Use after free in GPU
chromium-browser: Use after free in GPU
An use after free flaw was found in the GPU component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=489791425
Statement: Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
Chrome
Stable Channel Update for Desktop: CVE-2026-9111
vendor_chrome·2026-05-19·CVSS 4.2
CVE-2026-9111 [CRITICAL] Stable Channel Update for Desktop: CVE-2026-9111
Stable Channel Update for Desktop
CVE-2026-9111: Use after free in WebRTC. Reported by Google on 2026-04-20 [N/A][ 503551154 ] Critical CVE-2026-9110: Inappropriate implementation in UI
Reported by Google on 2026-04-20 [$11000][ 489791425 ] High CVE-2026-9112: Use after free in GPU
Severity: critical
VulDB
Google Chrome up to 148.0.7778.168 on Windows GPU use after free
vuldb·2026-05-20·CVSS 8.8
CVE-2026-9112 [HIGH] Google Chrome up to 148.0.7778.168 on Windows GPU use after free
A vulnerability marked as critical has been reported in Google Chrome on Windows. The impacted element is an unknown function of the component GPU. This manipulation causes use after free.
This vulnerability is handled as CVE-2026-9112. The attack can be initiated remotely. There is not any exploit available.
It is suggested to upgrade the affected component.
GHSA
GHSA-j2gw-w7xw-rj29: Use after free in GPU in Google Chrome on Windows prior to 148
ghsa_unreviewed·2026-05-20
CVE-2026-9112 [HIGH] CWE-416 GHSA-j2gw-w7xw-rj29: Use after free in GPU in Google Chrome on Windows prior to 148
Use after free in GPU in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-9110 CVE-2026-9111 CVE-2026-9112 CVE-2026-9113 CVE-2026-9114 CVE-2026-9115 CVE-2026-9116 CVE-2026-9117 CVE-2026-9118 CVE-2026-9119 CVE-2026-9120 CVE-2026-9121 CVE-2026-9122 CVE-2026-9123 CVE-
bugzilla·2026-05-28·CVSS 4.2
CVE-2026-9110 [MEDIUM] CVE-2026-9110 CVE-2026-9111 CVE-2026-9112 CVE-2026-9113 CVE-2026-9114 CVE-2026-9115 CVE-2026-9116 CVE-2026-9117 CVE-2026-9118 CVE-2026-9119 CVE-2026-9120 CVE-2026-9121 CVE-2026-9122 CVE-2026-9123 CVE-
CVE-2026-9110 CVE-2026-9111 CVE-2026-9112 CVE-2026-9113 CVE-2026-9114 CVE-2026-9115 CVE-2026-9116 CVE-2026-9117 CVE-2026-9118 CVE-2026-9119 CVE-2026-9120 CVE-2026-9121 CVE-2026-9122 CVE-2026-9123 CVE-2026-9124 ... chromium: various flaws [epel-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Bugzilla
CVE-2026-9110 CVE-2026-9111 CVE-2026-9112 CVE-2026-9113 CVE-2026-9114 CVE-2026-9115 CVE-2026-9116 CVE-2026-9117 CVE-2026-9118 CVE-2026-9119 CVE-2026-9120 CVE-2026-9121 CVE-2026-9122 CVE-2026-9123 CVE-
bugzilla·2026-05-28·CVSS 4.2
CVE-2026-9110 [MEDIUM] CVE-2026-9110 CVE-2026-9111 CVE-2026-9112 CVE-2026-9113 CVE-2026-9114 CVE-2026-9115 CVE-2026-9116 CVE-2026-9117 CVE-2026-9118 CVE-2026-9119 CVE-2026-9120 CVE-2026-9121 CVE-2026-9122 CVE-2026-9123 CVE-
CVE-2026-9110 CVE-2026-9111 CVE-2026-9112 CVE-2026-9113 CVE-2026-9114 CVE-2026-9115 CVE-2026-9116 CVE-2026-9117 CVE-2026-9118 CVE-2026-9119 CVE-2026-9120 CVE-2026-9121 CVE-2026-9122 CVE-2026-9123 CVE-2026-9124 ... chromium: various flaws [fedora-all]
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Bugzilla
CVE-2026-48710 starlette: Starlette: Security restriction bypass via malformed HTTP Host header
bugzilla·2026-05-26·CVSS 6.5
CVE-2026-48710 [MEDIUM] CVE-2026-48710 starlette: Starlette: Security restriction bypass via malformed HTTP Host header
CVE-2026-48710 starlette: Starlette: Security restriction bypass via malformed HTTP Host header
Starlette is a lightweight ASGI framework/toolkit. Prior to version 1.0.1, the HTTP `Host` request header was not validated before being used to reconstruct `request.url`. Because the routing algorithm relies on the raw HTTP path while `request.url` is rebuilt from the `Host` header, a malformed header could make `request.url.path` differ from the path that was actually requested. Middleware and endpoints that apply security restrictions based on `request.url` (rather than the raw `scope` path) could therefore be bypassed. Users should upgrade to a version greater than or equal to version 1.0.1, which validates the `Host` header against the grammar of RFC 9112 §3.2 / RFC 3986 §3.2.2 when constr
Bugzilla
CVE-2026-9112 chromium-browser: Use after free in GPU
bugzilla·2026-05-20·CVSS 8.8
CVE-2026-9112 [HIGH] CVE-2026-9112 chromium-browser: Use after free in GPU
CVE-2026-9112 chromium-browser: Use after free in GPU
Use after free in GPU in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Bugzilla
CVE-2026-39805 bandit: Bandit: HTTP Request Smuggling via Duplicate Content-Length Headers
bugzilla·2026-05-01·CVSS 6.3
CVE-2026-39805 [MEDIUM] CVE-2026-39805 bandit: Bandit: HTTP Request Smuggling via Duplicate Content-Length Headers
CVE-2026-39805 bandit: Bandit: HTTP Request Smuggling via Duplicate Content-Length Headers
Inconsistent Interpretation of HTTP Requests vulnerability in mtrudel bandit allows HTTP request smuggling via duplicate Content-Length headers.
'Elixir.Bandit.Headers':get_content_length/1 in lib/bandit/headers.ex uses List.keyfind/3, which returns only the first matching header. When a request contains two Content-Length headers with different values, Bandit silently accepts it, uses the first value to read the body, and dispatches the remaining bytes as a second pipelined request on the same keep-alive connection. RFC 9112 §6.3 requires recipients to treat this as an unrecoverable framing error.
When Bandit sits behind a proxy that picks the last Content-Length value and forwards the request ra
Bugzilla
CVE-2026-1760 libsoup: SoupServer: Denial of Service via HTTP request smuggling
bugzilla·2026-02-02·CVSS 5.3
CVE-2026-1760 [MEDIUM] CVE-2026-1760 libsoup: SoupServer: Denial of Service via HTTP request smuggling
CVE-2026-1760 libsoup: SoupServer: Denial of Service via HTTP request smuggling
HTTP request smuggling vulnerability in SoupServer due to improper handling of requests containing Transfer-Encoding: chunked combined with Connection: keep-alive. Although SoupServer correctly ignores the Content-Length header, it fails to close the connection after responding, in violation of RFC 9112. This allows remaining chunked data to be processed as a subsequent HTTP request. A remote, unauthenticated client can exploit this behavior to smuggle additional requests over a persistent connection, leading to unintended request processing and potential denial-of-service conditions.
2026-05-20
Published