NVD / CVE Program· CNA Chrome

CVE-2021-21112: Use after free in Blink in Google Chrome prior to 87.0.4280.141 allowed a remote attacker to potentially exploit heap corruption via a…

HighCVSS 8.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 35/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 1.3% (FIRST EPSS); higher than 72.2% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
Fixed version: chromium (Debian:10) 87.0.4280.141-0.1~deb10u1; chromium (Debian:12) 87.0.4280.141-0.1; chromium (openSUSE:Leap 15.1) 87.0.4280.141-lp151.2.165.1.

Low priority for now. Upgrade to chromium (Debian:10) 87.0.4280.141-0.1~deb10u1; chromium (Debian:12) 87.0.4280.141-0.1; chromium (openSUSE:Leap 15.1) 87.0.4280.141-lp151.2.165.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Use after free in Blink in Google Chrome prior to 87.0.4280.141 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Published: Jan 8, 2021
Updated: Jun 16, 2026
EPSS: 1.3% · 72th percentile
CWE: CWE-416

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.3%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
google	chrome	cpe:2.3:a:google:chrome
fedoraproject	fedora	cpe:2.3:o:fedoraproject:fedora
debian	debian linux	cpe:2.3:o:debian:debian_linux

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Chrome). Independent of NVD's CPE analysis and usually ahead of it.

Google Chrome
- unspecified and later · before 87.0.4280.141affected

Affected versions · NVD (4)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

debian debian linux10.0
fedoraproject fedora32
fedoraproject fedora33
google chromebefore 87.0.4280.141

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:10	chromium	before 87.0.4280.141-0.1~deb10u1	87.0.4280.141-0.1~deb10u1
Debian:12	chromium	before 87.0.4280.141-0.1	87.0.4280.141-0.1
openSUSE:Leap 15.1	chromium	before 87.0.4280.141-lp151.2.165.1	87.0.4280.141-lp151.2.165.1
openSUSE:Leap 15.1 NonFree	opera	before 73.0.3856.344-lp151.2.42.1	73.0.3856.344-lp151.2.42.1
openSUSE:Leap 15.2	chromium	before 87.0.4280.141-lp152.2.60.1	87.0.4280.141-lp152.2.60.1
openSUSE:Leap 15.2 NonFree	opera	before 73.0.3856.344-lp152.2.30.1	73.0.3856.344-lp152.2.30.1
SUSE:Package Hub 15 SP1	chromium	before 87.0.4280.141-bp151.3.150.1	87.0.4280.141-bp151.3.150.1
SUSE:Package Hub 15 SP2	chromium	before 87.0.4280.141-bp152.2.47.1	87.0.4280.141-bp152.2.47.1

Same product

google: all records

Other highest-scoring records for the same primary product.

CVE-2023-4863Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of…KEV
95Now
CVE-2021-21224Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a…KEV
90Now
CVE-2018-17463Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 allowed a remote attacker to execute arbitrary code inside a…KEV
90Now

Published before and after this one in the same product

← EarlierCVE-2021-21110Jan 8, 2021 · Use after free in safe browsing in Google Chrome prior to 87.0.4280.141 allowed a remote attacker to potentially perform a sandbox escape…
39Monitor
← EarlierCVE-2021-21111Jan 8, 2021 · Insufficient policy enforcement in WebUI in Google Chrome prior to 87.0.4280.141 allowed an attacker who convinced a user to install a…
38Monitor
Later →CVE-2021-21113Jan 8, 2021 · Heap buffer overflow in Skia in Google Chrome prior to 87.0.4280.141 allowed a remote attacker to potentially exploit heap corruption via a…
35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:chromium	87.0.4280.141-0.1 · Debian:12	Package registry (OSV)
opensuse:chromium	87.0.4280.141-lp152.2.60.1 · openSUSE:Leap 15.2	Package registry (OSV)
opensuse:opera	73.0.3856.344-lp151.2.42.1 · openSUSE:Leap 15.1 NonFree	Package registry (OSV)
suse:chromium	87.0.4280.141-bp151.3.150.1 · SUSE:Package Hub 15 SP1	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
A user must open a link or visit a page.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: Required
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1free(dev->buf);
2/* ... another thread is still running ... */
3process(dev->buf);

Fixed

1lock(&dev->lock);
2free(dev->buf);
3dev->buf = NULL;
4unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log (1)

Fix✗ → ✓Sep 28, 2026, 10:45 PM UTC

For records you follow, these changes also arrive as notifications. →

References

chromereleases.googleblog.com/2021/01/stable-channel-update-for-desktop.html

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records