Out of bounds write in Chrome OS Audio Server in Google Chrome on Chrome OS prior to 102.0.5005.125 allowed a remote attacker to potentiall…

published 2022-08-12 4y ago modified 2026-06-17 4mo ago also EUVD-2022-34836

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits: 0; none known

Out of bounds write in Chrome OS Audio Server in Google Chrome on Chrome OS prior to 102.0.5005.125 allowed a remote attacker to potentially exploit heap corruption via crafted audio metadata.

Patch / fix

fixed in 1

Google Chrome 102.0.5005.125

Is CVE-2022-2587 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Google Chrome

Classification

Weakness

CWE-787 Out-of-bounds Write

Technology feeds

Google Chrome rss critical rss

References

crbug.com /1320917
issue-tracking, permissions-required, vendor-advisory
chromereleases.googleblog.com /2022/06/stable-channel-update-for-chromeos.html
vendor-advisory

Sources

CVE List CVE-2022-2587
NVD CVE-2022-2587

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.