CVE-2026-9110
published 2026-05-20CVE-2026-9110: Inappropriate implementation in UI in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker who had compromised the renderer process to…
PriorityP420medium4.2CVSS 3.1
AVNACHPRNUIRSUCLINAL
EPSS
0.34%
26.3th percentile
Inappropriate implementation in UI in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Critical)
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| fastify | fastify | >= 5.7.2 < 5.8.1 | 5.8.1 |
| chrome | < 148.0.7778.179 | 148.0.7778.179 | |
| chrome | >= 148.0.7778.179 < 148.0.7778.179 | 148.0.7778.179 | |
| chrome_desktop | — | — | |
| nodejs | undici | >= 0 < 6.23.0 | 6.23.0 |
| nodejs | undici | >= 7.0.0 < 7.18.2 | 7.18.2 |
| paloalto | prisma_browser | — | — |
CVSS provenance
nvdv3.14.2MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:L
ghsa6.5MEDIUM
vendor_redhat5.3MEDIUM
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.
GHSA
GHSA-rgw2-264p-h9j3: Inappropriate implementation in UI in Google Chrome on Windows prior to 148
ghsa_unreviewed·2026-05-20
CVE-2026-9110 [MEDIUM] CWE-451 GHSA-rgw2-264p-h9j3: Inappropriate implementation in UI in Google Chrome on Windows prior to 148
Inappropriate implementation in UI in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Critical)
VulDB
Google Chrome up to 148.0.7778.168 on Windows UI ui layer
vuldb·2026-05-20·CVSS 4.2
CVE-2026-9110 [MEDIUM] Google Chrome up to 148.0.7778.168 on Windows UI ui layer
A vulnerability labeled as problematic has been found in Google Chrome on Windows. The affected element is an unknown function of the component UI. The manipulation results in improper restriction of rendered ui layers.
This vulnerability is known as CVE-2026-9110. It is possible to launch the attack remotely. No exploit is available.
The affected component should be upgraded.
GHSA
Hono's Cache Middleware ignores Vary: Authorization / Vary: Cookie leading to cross-user cache leakage
ghsa·2026-05-09
CVE-2026-44457 [MEDIUM] CWE-524 Hono's Cache Middleware ignores Vary: Authorization / Vary: Cookie leading to cross-user cache leakage
Hono's Cache Middleware ignores Vary: Authorization / Vary: Cookie leading to cross-user cache leakage
### Summary
Cache Middleware does not skip caching for responses that declare per-user variance via `Vary: Authorization` or `Vary: Cookie`. As a result, a response cached for one authenticated user may be served to subsequent requests from different users.
### Details
The Cache Middleware skips caching when a response carries `Vary: *`, certain `Cache-Control` directives (`private`, `no-store`, `no-cache`), or `Set-Cookie`. However, `Vary: Authorization` and `Vary: Cookie` — the standard signals defined in RFC 9110 / RFC 9111 to indicate per-user responses — are not treated as cache-skip reasons.
This issue arises when applications use the Cache Middleware on endpoints that return u
GHSA
Netty: HTTP Request Smuggling via Chunked Extension Quoted-String Parsing
ghsa·2026-03-26
CVE-2026-33870 [HIGH] CWE-444 Netty: HTTP Request Smuggling via Chunked Extension Quoted-String Parsing
Netty: HTTP Request Smuggling via Chunked Extension Quoted-String Parsing
## Summary
Netty incorrectly parses quoted strings in HTTP/1.1 chunked transfer encoding extension values, enabling request smuggling attacks.
## Background
This vulnerability is a new variant discovered during research into the "Funky Chunks" HTTP request smuggling techniques:
-
-
The original research tested various chunk extension parsing differentials but did not cover quoted-string handling within extension values.
## Technical Details
**RFC 9110 Section 7.1.1** defines chunked transfer encoding:
```
chunk = chunk-size [ chunk-ext ] CRLF chunk-data CRLF
chunk-ext = *( BWS ";" BWS chunk-ext-name [ BWS "=" BWS chunk-ext-val ] )
chunk-ext-val = token / quoted-string
```
**RFC 9110 Section 5.6.4** defines
GHSA
Fastify's Missing End Anchor in "subtypeNameReg" Allows Malformed Content-Types to Pass Validation
ghsa·2026-03-05
CVE-2026-3419 [MEDIUM] CWE-185 Fastify's Missing End Anchor in "subtypeNameReg" Allows Malformed Content-Types to Pass Validation
Fastify's Missing End Anchor in "subtypeNameReg" Allows Malformed Content-Types to Pass Validation
# Description
Fastify incorrectly accepts malformed `Content-Type` headers containing trailing characters after the subtype token, in violation of [RFC 9110 §8.3.1](https://httpwg.org/specs/rfc9110.html#field.content-type). For example, a request sent with `Content-Type: application/json garbage` passes validation and is processed normally, rather than being rejected with `415 Unsupported Media Type`.
When regex-based content-type parsers are in use (a documented Fastify feature), the malformed value is matched against registered parsers using the full string including the trailing garbage. This means a request with an invalid content-type may be routed to and processed by a parser it shou
GHSA
Undici has an unbounded decompression chain in HTTP responses on Node.js Fetch API via Content-Encoding leads to resource exhaustion
ghsa·2026-01-14·CVSS 6.5
CVE-2026-22036 [MEDIUM] CWE-770 Undici has an unbounded decompression chain in HTTP responses on Node.js Fetch API via Content-Encoding leads to resource exhaustion
Undici has an unbounded decompression chain in HTTP responses on Node.js Fetch API via Content-Encoding leads to resource exhaustion
### Impact
The `fetch()` API supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, br). This is also supported by the undici decompress interceptor.
However, the number of links in the decompression chain is unbounded and the default maxHeaderSize allows a malicious server to insert thousands compression steps leading to high CPU usage and excessive memory allocation.
### Patches
Upgrade to 7.18.2 or 6.23.0.
### Workarounds
It is possible to apply an undici interceptor and filter long `Content-Encoding` sequences manually.
### References
* https://hackerone.com/reports/3456148
* https://gi
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
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
Red Hat
chromium-browser: Inappropriate implementation in UI
vendor_redhat·2026-05-19·CVSS 4.2
CVE-2026-9110 [MEDIUM] CWE-1021 chromium-browser: Inappropriate implementation in UI
chromium-browser: Inappropriate implementation in UI
An inappropriate implementation flaw was found in the UI component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=503551154
Statement: Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
Red Hat
fastify: Fastify: Bypass of Content-Type validation via malformed Content-Type headers
vendor_redhat·2026-03-06·CVSS 5.3
CVE-2026-3419 [MEDIUM] CWE-625 fastify: Fastify: Bypass of Content-Type validation via malformed Content-Type headers
fastify: Fastify: Bypass of Content-Type validation via malformed Content-Type headers
Fastify incorrectly accepts malformed `Content-Type` headers containing trailing characters after the subtype token, in violation of RFC 9110 §8.3.1(https://httpwg.org/specs/rfc9110.html#field.content-type). For example, a request sent with Content-Type: application/json garbage passes validation and is processed normally, rather than being rejected with 415 Unsupported Media Type.
When regex-based content-type parsers are in use (a documented Fastify feature), the malformed value is matched against registered parsers using the full string including the trailing garbage. This means a request with an invalid content-type may be routed to and processed by a parser it should never have reached.
Impact:
An
No detection rules found.
No public exploits indexed.
Hackernews
⚡ Weekly Recap: Linux Flaws, Defender 0-Days, Router Botnets, and Supply Chain Chaos
blogs_hackernews·2026-05-25
CVE-2026-46333 ⚡ Weekly Recap: Linux Flaws, Defender 0-Days, Router Botnets, and Supply Chain Chaos
Home
Threat Intelligence
Vulnerabilities
Cyber Attacks
Webinars
Expert Insights
Awards
Webinars
Awards
Free eBooks
About THN
Jobs
Advertise with us
## ⚡ Weekly Recap: Linux Flaws, Defender 0-Days, Router Botnets, and Supply Chain Chaos
Monday recap. Same mess, new week.
A sketchy dev tool got people pwned, old bugs came back from the dead, and security products somehow needed protecting from themselves. A bunch of companies spent the week checking old boxes and forgotten servers they should've patched years ago. Good times.
Phishing crews are getting smarter too - less obvious scam junk, more targeted stuff that actually looks real. Meanwhile, botnets are grabbing anything exposed to the internet like it's free candy. The Internet's still a dumpster fire.
Let’s get into
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-9110 chromium-browser: Inappropriate implementation in UI
bugzilla·2026-05-20·CVSS 4.2
CVE-2026-9110 [MEDIUM] CVE-2026-9110 chromium-browser: Inappropriate implementation in UI
CVE-2026-9110 chromium-browser: Inappropriate implementation in UI
Inappropriate implementation in UI in Google Chrome on Windows prior to 148.0.7778.179 allowed a remote attacker who had compromised the renderer process to perform UI spoofing via a crafted HTML page. (Chromium security severity: Critical)
2026-05-20
Published