CVE-2026-9989
published 2026-05-28CVE-2026-9989: Inappropriate implementation in Media in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to bypass same origin policy via a crafted video file…
PriorityP431medium6.3CVSS 3.1
AVNACLPRNUIRSUCLILAL
EPSS
0.11%
1.3th percentile
Inappropriate implementation in Media in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to bypass same origin policy via a crafted video file. (Chromium security severity: High)
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | < 148.0.7778.216 | 148.0.7778.216 | |
| chrome | < 148.0.7778.215 | 148.0.7778.215 | |
| chrome | >= 148.0.7778.216 < 148.0.7778.216 | 148.0.7778.216 | |
| chrome_desktop | — | — | |
| paloalto | prisma_browser | — | — |
CVSS provenance
nvdv3.16.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
vendor_redhat6.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.
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-9989
vendor_chrome·2026-05-27
CVE-2026-9989 [HIGH] Stable Channel Update for Desktop: CVE-2026-9989
Stable Channel Update for Desktop
CVE-2026-9989: Inappropriate implementation in Media. Reported by Google on 2026-05-14 [N/A][ 513128608 ] High CVE-2026-9990: Use after free in WebAppInstalls
Reported by Google on 2026-05-14 [N/A][ 513173565 ] High CVE-2026-9991: Inappropriate implementation in Media
Severity: high
Red Hat
chromium-browser: Inappropriate implementation in Media
vendor_redhat·2026-05-27·CVSS 6.3
CVE-2026-9989 [MEDIUM] CWE-346 chromium-browser: Inappropriate implementation in Media
chromium-browser: Inappropriate implementation in Media
An inappropriate implementation flaw was found in the Media component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=513054053
Statement: Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.
GHSA
GHSA-8g45-3jxc-cv2v: Inappropriate implementation in Media in Google Chrome prior to 148
ghsa_unreviewed·2026-05-29
CVE-2026-9989 [MEDIUM] CWE-346 GHSA-8g45-3jxc-cv2v: Inappropriate implementation in Media in Google Chrome prior to 148
Inappropriate implementation in Media in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to bypass same origin policy via a crafted video file. (Chromium security severity: High)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2026-9989 chromium-browser: Inappropriate implementation in Media
bugzilla·2026-05-28
CVE-2026-9989 [HIGH] CVE-2026-9989 chromium-browser: Inappropriate implementation in Media
CVE-2026-9989 chromium-browser: Inappropriate implementation in Media
Inappropriate implementation in Media in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to bypass same origin policy via a crafted video file. (Chromium security severity: High)
Bugzilla
CVE-2026-43285 kernel: mm/slab: do not access current->mems_allowed_seq if !allow_spin
bugzilla·2026-05-08
CVE-2026-43285 CVE-2026-43285 kernel: mm/slab: do not access current->mems_allowed_seq if !allow_spin
CVE-2026-43285 kernel: mm/slab: do not access current->mems_allowed_seq if !allow_spin
In the Linux kernel, the following vulnerability has been resolved:
mm/slab: do not access current->mems_allowed_seq if !allow_spin
Lockdep complains when get_from_any_partial() is called in an NMI
context, because current->mems_allowed_seq is seqcount_spinlock_t and
not NMI-safe:
WARNING: inconsistent lock state
6.19.0-rc5-kfree-rcu+ #315 Tainted: G N
inconsistent {INITIAL USE} -> {IN-NMI} usage.
kunit_try_catch/9989 [HC1[1]:SC0[0]:HE0:SE1] takes:
ffff889085799820 (&____s->seqcount#3){.-.-}-{0:0}, at: ___slab_alloc+0x58f/0xc00
{INITIAL USE} state was registered at:
lock_acquire+0x185/0x320
kernel_init_freeable+0x391/0x1150
kernel_init+0x1f/0x220
ret_from_fork+0x736/0x8f0
ret_from_fork_asm+0x1a/0x30
2026-05-28
Published