nday
CVE-2025-14174

Google Chromium Out of Bounds Memory Access Vulnerability

Google / Chromium, Chrome

Added to CISA KEV on the day of disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

buffer overflow / out-of-bounds write
CWE-119, stated by the ADP CISA-ADP and NVD, republishing 134c704f-9b21-4f2e-91b3-4a467353bcc0CWE-787, stated by NVD's analysts
network
AV:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the ADP CISA-ADP
no authentication required
PR:N in CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (CVSS 3.1) from the ADP CISA-ADP
macOS
CPE names NVD's analysts give as vulnerable: o:apple:macos
iOS / iPadOS
CPE names NVD's analysts give as vulnerable: o:apple:ipados, o:apple:iphone_os
watchOS
CPE names NVD's analysts give as vulnerable: o:apple:watchos
tvOS
CPE names NVD's analysts give as vulnerable: o:apple:tvos
visionOS
CPE names NVD's analysts give as vulnerable: o:apple:visionos
Chrome
affected products in the CVE record: Google · ChromeCPE names NVD's analysts give as vulnerable: a:google:chrome
Safari
CPE names NVD's analysts give as vulnerable: a:apple:safari
Microsoft Edge
CPE names NVD's analysts give as vulnerable: a:microsoft:edge_chromium
operating system
CPE names NVD's analysts give as vulnerable: o:apple:ipados, o:apple:iphone_os, o:apple:macos, o:apple:tvos, o:apple:visionos, o:apple:watchosthe product type of iOS / iPadOS, macOS, tvOS, visionOS, and watchOS in nday's product registry
browser
affected products in the CVE record: Google · ChromeCPE names NVD's analysts give as vulnerable: a:apple:safari, a:google:chrome, a:microsoft:edge_chromiumthe product type of Chrome, Microsoft Edge, and Safari in nday's product registry
stage
KEV
disclosed
cvss
8.8 HIGH v3.1
KEV due date
2026-01-02

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2025-12-12T19:20Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
≤ 2025-12-12, inferred from KEV
KEVKEV
2025-12-12, date only

Summary

Out of bounds memory access in ANGLE in Google Chrome on Mac prior to 143.0.7499.110 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:N
Network: the attacker only needs to reach it over the network
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:N
None: no account or authorization needed
User interaction UI:R
Required: a user must do something, such as open a file or click a link

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS 3.1 vector from the CVE record, added by the ADP CISA-ADP.

Event log

2025-12-12date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2026-01-02. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 306,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2025-12-12T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [],
    "notes": "https://chromereleases.googleblog.com/2025/12/stable-channel-update-for-desktop_10.html ; https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnotes-security ; https://nvd.nist.gov/vuln/detail/CVE-2025-14174",
    "product": "Chromium",
    "due_date": "2026-01-02",
    "precision": "day",
    "date_added": "2025-12-12",
    "vendor_project": "Google",
    "forensic_triage": "No",
    "required_action": "Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.",
    "vulnerability_name": "Google Chromium Out of Bounds Memory Access Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2025-12-12inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

+DISdisclosed

CVE record published by Chrome. CVSS 8.8, high. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 17558,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2025-14174",
  "occurred_at": "2025-12-12T19:20:41.809Z",
  "observed_at": "2026-11-12T15:01:53.938848Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-14174",
      "date_added": "2025-12-12"
    },
    "cvss": {
      "source": "adp:CISA-ADP",
      "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H",
      "version": "3.1",
      "base_score": 8.8,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2025-12-16T04:55:55.101177Z",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2025-12-12T19:20:41.809Z",
    "assigner_short_name": "Chrome"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.