basicsecurity.net
Proof, not just disclosure.
Threats / Google / CVE-2021-37976
CVE-2021-37976 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Google Chromium vulnerability

Google Chromium contains an information disclosure vulnerability allowing remote attackers to obtain sensitive data from process memory via crafted HTML pages.

Verdict

Today item — known-exploited.

A remote attacker can craft malicious HTML to trigger memory disclosure in Chromium-based browsers, potentially exposing sensitive information from the affected process without requiring user interaction beyond visiting a webpage.

CISA KEV Yes · 2021-11-033EPSS 0.19901 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
5 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.19901 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Google, Chromium. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-862 Missing Authorization — weakness family: Authorization / access control.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-862 · Missing AuthorizationAuthorization / access control
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious HTML page containing code that triggers the memory disclosure vulnerability in Chromium.
Business
User visits the attacker's webpage and sensitive data from browser process memory is exposed to the attacker.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I host the exploit on a website or distribute it through compromised legitimate sites to maximize exposure.
Business
Widespread user exposure increases the likelihood of capturing sensitive information such as authentication tokens, encryption keys, or personal data from multiple victims.
3

Lateral reach — past segmentation narrative 3

Attacker
I extract and analyze the disclosed memory contents to identify valuable data like credentials or session information.
Business
Compromised credentials or session tokens enable account takeover, unauthorized access to user services, and potential lateral movement into connected systems.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 5 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by Chrome (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by ChromeCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.