VDB
CVE-2022-0291
CVE-2022-0291
PUBLISHED
Reported by chrome · Published February 12, 2022
Inappropriate implementation in Storage in Google Chrome prior to 97.0.4692.99 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| qt5-qtwebengine | Alpine | 5.15.3_git20220121-r4, 5.15.3_git20211127-r4 |
| chrome | 97.0.4692.99 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Chrome | unspecified | |
| alpine | qt5-qtwebengine | 0, 0 |
| Chrome | * |
Timeline
- Jan 20, 2022 CVE Published
- Feb 12, 2022 EPSS Score (30 in total, the first dated here)
- Jan 17, 2025 PoC Published (2 in total, the first dated here)
- Jun 1, 2026 Security Advisory (4 in total, the first dated here)
- Jul 13, 2026 Coalition ESS Score
- Sep 20, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2022-0291
vulnetix vdb fixes CVE-2022-0291
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2022-0291/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart