cve.bz

CVE-2025-12433 google chrome

4.3 mediumEPSS 0.3%

Medium (4.3) in google chrome. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Inappropriate implementation in V8 in Google Chrome prior to 142.0.7444.59 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 22nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-11-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-12433 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-12433?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-12433?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-12433 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromefrom 142.0.7444.59 before 142.0.7444.59

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12chromium142.0.7444.59-1~deb12u1DEBIAN-CVE-2025-12433 DSA-6046-1
Debian13chromium142.0.7444.59-1~deb13u1DEBIAN-CVE-2025-12433 DSA-6046-1
Debian14chromium142.0.7444.59-1DEBIAN-CVE-2025-12433
openSUSELeap 16.0chromium142.0.7444.162-bp160.1.1openSUSE-SU-2025:20076-1
openSUSETumbleweedchromium142.0.7444.59-2.1openSUSE-SU-2025:15687-1
Alpinev3.22qt6-qtwebengine6.8.3-r6ALPINE-CVE-2025-12433
Alpinev3.23, v3.24qt6-qtwebengine6.10.0-r1ALPINE-CVE-2025-12433
Azure Linux2nodejs18no fix listedAZL-70393

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · openSUSE · Alpine.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-12433.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • jamezx32/CVE-2025-12433 Harbor Check: matches CVE 0 stars, JavaScript, created
    V8 hole-check elision merge bug - PoC + exploit

References

Check your stackJSON