LiveActive security incident?Get immediate response
CVE Record

CVE-2021-37976: Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to...

Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to obtain potentially sensitive information from process memory via a crafted HTML page.

MediumCVSS 6.5Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Chrome flaw could let a malicious webpage read sensitive data from browser process memory. A user would need to open the crafted page, but no login or special access is required. Because CISA lists it in KEV, treat outdated Chrome or Chromium installations as urgent to find and remediate.

Executive priority

Prioritize this above ordinary medium CVSS browser bugs because it is in CISA KEV. The business risk is sensitive information exposure from user browsing activity on unpatched systems, not service outage. Remediation should be handled as endpoint hygiene with executive visibility until fleet coverage is confirmed.

Technical view

CVE-2021-37976 is an inappropriate memory implementation issue in Google Chrome before 94.0.4606.71. The CVSS vector is network, low complexity, no privileges, user interaction required, with high confidentiality impact and no integrity or availability impact. Sources describe exposure through a crafted HTML page.

Likely exposure

Exposure is most likely on endpoints, VDI images, kiosks, or Linux systems running Chrome or Chromium builds older than 94.0.4606.71. Fedora and Debian advisories indicate distribution-packaged Chromium also required updates. Current, auto-updating browser fleets are less likely exposed.

Exploitation context

CISA KEV identifies this CVE as known exploited. The source bundle does not provide exploit details, campaign context, or public proof-of-concept evidence. The Google bug reference is cited, but detailed technical information may be restricted or incomplete.

Researcher notes

The public description supports an information disclosure issue, not code execution. The CWE entry is CWE-862, though the description centers on memory handling. Available sources do not include exploit mechanics, affected subcomponents beyond Chrome memory handling, or detailed indicators of compromise.

Mitigation direction

  • Update Google Chrome or Chromium to 94.0.4606.71 or later.
  • Apply relevant Fedora, Debian, or other vendor browser package updates.
  • Enforce browser auto-update and block unsupported browser versions.
  • Prioritize remediation for internet-facing user workstations and managed shared systems.
  • Check current vendor guidance for any platform-specific remediation details.

Validation and detection

  • Inventory Chrome and Chromium versions across managed endpoints.
  • Confirm no systems run versions older than 94.0.4606.71.
  • Verify Linux package versions match patched vendor advisories.
  • Track remediation against the CISA KEV entry.
  • Review browser update compliance for offline, kiosk, and VDI images.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-37976 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
Yes
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
8Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-37976Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChromeunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.