What this access enables
- Temporarily gain host access to the active tab after an invoking gesture, enabling many “one-shot” tools (capture, translate selection, DOM helpers).
- Often pairs with scripting APIs for that tab without declaring `<all_urls>` in the manifest.
If it is abused or compromised
- Still dangerous if combined with exfiltration channels (downloads, native messaging, or broad network permissions).
- Confusing UX: users may not realize a second permission quietly broadens scope beyond activeTab.
Evidence, documentation, and reporting
Official semantics
Chromium documents activeTab alongside the permissions list; read the precise grant conditions before trusting UI copy in the store.Sources: Chrome — Permissions list (activeTab entry) · Chrome — Declare permissions
MDN describes the Firefox-flavored behavior for comparison when you audit cross-browser add-ons.Sources: MDN — activeTab (Firefox)
Practical mitigations
- Favor extensions that rely on activeTab alone when the feature is inherently “on-demand.”
- Re-scan the permission diff after each update.
- If an on-demand tool also requests “all sites,” ask why both are necessary.
Frequently asked questions
Concise answers for this permission class—use with the evidence and mitigations above for full context and citations.
Further reading (curated)
Mix of vendor documentation, standards-style guidance, independent research, and news investigations—each page below is a different angle on the same permission class.
- Chrome — Permissions list
- Chrome — scripting API
- Chrome — Declare permissions
- MDN — activeTab permission
- W3C — User interaction / HTML living standard (gesture concepts)
- OWASP — Client-side security (overview)
- USENIX ;login — usable security columns (context)
- IEEE S&P (conference hub)
- Chrome Developers — Extension MV3 migration primer
- Mozilla — Request the right permissions
- web.dev — Secure cross-origin browser features
Related extension guides
These topics often show up together in real extensions and abuse reporting—reading them as a set makes it easier to judge combined risk.
- “Read and change all your data on every website” — what it really means
Plain-language deep dive on host permissions that cover every website: capabilities, real abuse cases, Chrome/Mozilla documentation, and independent research citations.
- Browser extensions & open tabs (full guide)
How extension tab permissions work (open tabs, URLs, navigation): capabilities, documented incidents with cited user counts, token-in-URL risks, and mitigations.
- Browser extensions & scripts / DOM (full guide)
Content scripts, scripting API, what “read and change all your data” means, cited incidents, and how to reduce scope.
Audit what is installed
Pair least-privilege installs with a periodic review—especially after any extension update.