CORS enforcement for Background Fetch
- Category
- Security
- Type
- New or changed feature
- Status
- Proposed (Chrome Proposed)
- Intent stage
- None
Summary
Starting in Chrome 157, the Background Fetch API now enforces Cross-Origin Resource Sharing (CORS). This update aligns Chromium's implementation with the intent of the [Background Fetch spec](https://wicg.github.io/background-fetch/). This ensures that Background Fetch requests are subject to the same security policies as regular Fetch requests, such as Local Network Access checks. This update prevents sites from bypassing CORS (and other security policy checks) by using Background Fetch instead of regular [Fetch](https://fetch.spec.whatwg.org/).
Motivation
This fixes a security issue where Background Fetch unintentionally bypasses security policies such as CORS (and CORP/COEP/DIP). (crbug.com/515243254 is our meta bug tracking all of the different web platform security issues with Background Fetch.)
Standards & signals
- Specification: https://wicg.github.io/background-fetch
- Firefox: No signal
- Safari: No signal
- Web developers: No signals
Ecosystem
- Web Platform Tests: https://wpt.fyi/results/?q=cors-enforcement-for-background-fetch
- Chrome Platform Showcase: https://chrome-platform-showcase.paulkinlan-ea.deno.net/features
- GenDN reference: https://gendn.paulkinlan-ea.deno.net/features
- chrome.dev demos search: https://www.google.com/search?q=site%3Achrome.dev+CORS%20enforcement%20for%20Background%20Fetch
- MDN Web Docs: https://developer.mozilla.org/en-US/search?q=CORS%20enforcement%20for%20Background%20Fetch
- Baseline status: https://webstatus.dev/?q=CORS%20enforcement%20for%20Background%20Fetch