CVE-2021-37980: Inappropriate implementation in Sandbox in Google Chrome prior to 94.0.4606.81 allowed a remote attacker to potentially bypass site…
Noroxi assessment
Priority: Monitor (action score 29/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.4% (FIRST EPSS); higher than 73.9% 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: qt5-qtwebengine (Alpine:v3.14) 5.15.3_git20211006-r1; qt5-qtwebengine (Alpine:v3.15) 5.15.3_git20211006-r3; chromium (Debian:12) 97.0.4692.71-0.1.
Low priority for now. Upgrade to qt5-qtwebengine (Alpine:v3.14) 5.15.3_git20211006-r1; qt5-qtwebengine (Alpine:v3.15) 5.15.3_git20211006-r3; chromium (Debian:12) 97.0.4692.71-0.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
Inappropriate implementation in Sandbox in Google Chrome prior to 94.0.4606.81 allowed a remote attacker to potentially bypass site isolation via Windows.
- Published
- Nov 2, 2021
- Updated
- Jun 17, 2026
- EPSS
- 1.4% · 73th percentile
- CWE
- —
Report tools
Action score
29
Low priority for now.
- CVSS
- 29 / 40 · 7.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi 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 helpAffected 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 |
|---|---|---|
| chrome | cpe:2.3:a:google:chrome | |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
| 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 94.0.4606.81affected
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
- debian debian linux11.0
- fedoraproject fedora33
- google chromebefore 94.0.4606.81
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.14 | qt5-qtwebengine | before 5.15.3_git20211006-r1 | 5.15.3_git20211006-r1 |
| Alpine:v3.15 | qt5-qtwebengine | before 5.15.3_git20211006-r3 | 5.15.3_git20211006-r3 |
| Debian:12 | chromium | before 97.0.4692.71-0.1 | 97.0.4692.71-0.1 |
| openSUSE:Leap 15.2 NonFree | opera | before 80.0.4170.63-lp152.2.73.1 | 80.0.4170.63-lp152.2.73.1 |
| openSUSE:Leap 15.3 NonFree | opera | before 80.0.4170.63-lp153.2.27.1 | 80.0.4170.63-lp153.2.27.1 |
| openSUSE:Leap 15.3 NonFree | opera | before 83.0.4254.27-lp153.2.33.1 | 83.0.4254.27-lp153.2.33.1 |
| openSUSE:Tumbleweed | chromium | before 94.0.4606.81-1.1 | 94.0.4606.81-1.1 |
Same product
google: all recordsOther 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…KEV95Now
- 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…KEV90Now
- 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…KEV90Now
Published before and after this one in the same product
- ← EarlierCVE-2021-37978Nov 2, 2021 · Heap buffer overflow in Blink in Google Chrome prior to 94.0.4606.81 allowed a remote attacker to potentially exploit heap corruption via a…35Monitor
- ← EarlierCVE-2021-37979Nov 2, 2021 · heap buffer overflow in WebRTC in Google Chrome prior to 94.0.4606.81 allowed a remote attacker who convinced a user to browse to a…36Monitor
- Later →CVE-2021-37981Nov 2, 2021 · Heap buffer overflow in Skia in Google Chrome prior to 95.0.4638.54 allowed a remote attacker who had compromised the renderer process to…38Monitor
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 |
|---|---|---|
| alpine:qt5-qtwebengine | 5.15.3_git20211006-r1 · Alpine:v3.14 | Package registry (OSV) |
| debian:chromium | 97.0.4692.71-0.1 · Debian:12 | Package registry (OSV) |
| opensuse:chromium | 94.0.4606.81-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:opera | 80.0.4170.63-lp152.2.73.1 · openSUSE:Leap 15.2 NonFree | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:70 | 2021-10-12 |
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.
- First PoC-22 d
- Published
- TodayNov 12, 2026+1836 d
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
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
nvd-primary
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✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.