CVE-2026-0899General(apple / chrome)

LOWCVSS 8.8 · HIGH

Exploit discussion active in current signal (1 latest mentions)

Immediate actions

Patch apple chrome systems immediately
Hunt for exploitation attempts and persistence artifacts
Increase monitoring for publicly documented tradecraft

Recommended action window: High priority (within 72h)

NVD description

Out of bounds memory access in V8 in Google Chrome prior to 144.0.7559.59 allowed a remote attacker to potentially exploit object corruption via a crafted HTML page. (Chromium security severity: High)

apple CVEs Back to dashboard

3.0/ 10 priority

Sources & remediation

Vendor / third-party advisories

https://chromereleases.googleblog.com/2026/01/stable-channel-update-for-desktop_13.html

Other references

https://issues.chromium.org/issues/458914193

Weakness type (CWE)

CWE-125CWE-787

Priority

LOW

Exploitation

NONE

PoC

YES

Patch

AVAILABLE

Momentum

STABLE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

chrome
linux_kernel
macos
windows

Threat summary

Public PoC is present in monitored signal
Patch or workaround signal is available
5 mentions across 4 observed days
Momentum state: stable

What's happening

PoC mentioned or linked in 1 signal
Patch or workaround mentioned in 1 signal
Technical details provided in 3 signals
General: 2 classified signals
Disclosure: 1 classified signal
Peaked 2d ago at 2 mentions (2026-04-01); latest day: 1
5 total mentions across 4 days

Affected systems

Vendors

apple google linux microsoft

Products

chromelinux_kernelmacoswindows

1 version affected across 4 products

Deep dive

Activity timeline5 mentions / 4d

Signal classification4 categories

General

240.0%

Patch

120.0%

Disclosure

120.0%

PoC

120.0%

Referenced assets2 URLs

By indicator

Classification over time

Date	Total	Labels

2026-03-09	1	Patch1
2026-04-01	2	Disclosure1General1
2026-04-08	1	General1
2026-04-17	1	PoC1

Full discourse5 posts

starlabs@starlabs_sg192d
General
Our newest team member @streypaws just dropped his first blog post! He peered into CVE-2026-0899, from patch to arbitrary r/w primitives No, it is not April Fool's joke from us https://starlabs.sg/blog/2026/04-check-removed-context-confused-checkmate-achieved/
Post summary
The post references CVE‑2026‑0899 and notes it provides arbitrary read/write primitives, but no PoC, exploit tools, active exploitation, or patch information is provided.
33301656611.1K
10.0K followersView on X
0xor0ne@0xor0ne177d
PoC
Exploiting CVE-2026-0899, an Out-of-Bounds memory access in Chrome V8 https://starlabs.sg/blog/2026/04-check-removed-context-confused-checkmate-achieved/ Research by Shreyas Penkar (@streypaws) (@starlabs_sg) #infosec
Post summary
The text announces research on CVE-2026-0899, an out-of-bounds memory access in Chrome V8, providing a link to a blog post that likely contains a Proof of Concept.
0170107637.2K
91.5K followersView on X
p1nky@p1nky4745185d
General
Great research by @streypaws on CVE-2026-0899 https://starlabs.sg/blog/2026/04-check-removed-context-confused-checkmate-achieved/
Post summary
The tweet merely references research on CVE‑2026‑0899, with no detailed technical information, exploit availability, or remediation guidance.
01120140
33 followersView on X
White Rabbitx@TheRabbitPy215d
Patch
BSI warns of critical vulns in Chrome/Edge (CVE-2026-0899 to CVE-2026-0908). Update browsers now to block potential attacks. Affects multiple Chromium versions. https://borncity.com/news/browsersicherheit-bsi-warnt-vor-kritischen-luecken-in-chrome-und-edge/
Post summary
BSI has issued a warning about critical Chrome/Edge vulnerabilities (CVE‑2026‑0899 to CVE‑2026‑0908) and urges users to immediately update their browsers to protect against potential attacks.
0001033
55 followersView on X
Autumn Good@autumn_good_35192d
Disclosure
『A function literal ID mismatch caused by the parser’s failure to pre-allocate the “other” initializer scope when reparsing one initializer, lead to incorrect ID assignment』 CVE-2026-0899 CHECK Removed, Context Confused, Checkmate Achieved | STAR Labs https://starlabs.sg/blog/2026/04-check-removed-context-confused-checkmate-achieved/
Post summary
The passage explains a parser bug behind CVE-2026-0899, providing technical details but offering no PoC, exploit, active exploitation, patch, or false positive claim.
00000405
6.7K followersView on X

CPE platform detail4 entries

Part:

Vendor:

Product:

Version:

Target SW:

Target HW:

4 of 4 entries

Part	Vendor	Product	Version	Target SW	Target HW
OS	apple	macos	-	-	-
App	google	chrome	-	-	-
OS	linux	linux_kernel	-	-	-
OS	microsoft	windows	-	-	-

Explore more

Back to dashboard apple CVEs google CVEs linux CVEs chrome vulnerabilities

What researchers are saying

CVE-2026-0899

0xor0ne[verified]@0xor0nePoC

The text announces research on CVE-2026-0899, an out-of-bounds memory access in Chrome V8, providing a link to a blog post that likely contains a Proof of Concept.

White Rabbitx[verified]@TheRabbitPyPatch

BSI has issued a warning about critical Chrome/Edge vulnerabilities (CVE‑2026‑0899 to CVE‑2026‑0908) and urges users to immediately update their browsers to protect against potential attacks.

starlabs@starlabs_sgGeneral

The post references CVE‑2026‑0899 and notes it provides arbitrary read/write primitives, but no PoC, exploit tools, active exploitation, or patch information is provided.

p1nky@p1nky4745General

The tweet merely references research on CVE‑2026‑0899, with no detailed technical information, exploit availability, or remediation guidance.

Autumn Good@autumn_good_35Disclosure

The passage explains a parser bug behind CVE-2026-0899, providing technical details but offering no PoC, exploit, active exploitation, patch, or false positive claim.