VDB
CVE-2023-4367
CVE-2023-4367
PUBLISHED
Reported by chrome · Published August 15, 2023
Insufficient policy enforcement in Extensions API in Google Chrome prior to 116.0.5845.96 allowed an attacker who convinced a user to install a malicious extension to bypass an enterprise policy via a crafted HTML page. (Chromium security severity: Medium)
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Chrome | 116.0.5845.96 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Chrome | 116.0.5845.96 | |
| Chrome | 116.0.5845.96 |
Timeline
- Aug 15, 2023 CVE Published
- Aug 16, 2023 EPSS Score (30 in total, the first dated here)
- Feb 13, 2025 CVE Updated
- Mar 11, 2026 Distribution Patch
- Mar 11, 2026 Security Advisory (6 in total, the first dated here)
- Aug 2, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2023-4367
vulnetix vdb fixes CVE-2023-4367Or 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-2023-4367/fixes/registry"The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart