Manifest V3 lowers risk by limiting persistent background execution, tightening permissions, and disallowing remotely hosted code. Those controls reduce opportunities for unreviewed logic to run inside the extension and make it harder for an attacker to inject or modify behavior after release. The model is stronger when sensitive functions stay packaged, reviewed, and contained inside the extension itself.
How Manifest V3 changes the attack surface of an extension
Manifest V3 reduces risk by changing what an extension can do at runtime, not by making extension code inherently safe. The biggest shift is that the extension has less freedom to keep running in the background, reach out for new code, or quietly expand its behavior after publication. That matters because secrets are only as safe as the smallest set of code paths that can touch them.
For a secrets-handling extension, the practical question is whether the secret-processing logic remains reviewable and bounded. When the extension cannot keep an always-on background page or fetch fresh executable logic from elsewhere, it becomes harder for hidden behaviour to persist or for a later compromise to change how tokens, session data, or API keys are handled.
Manifest V3 also pushes teams toward clearer permission boundaries. That is useful when an extension needs access to sensitive pages, storage, or browser capabilities, because overbroad permissions are often what turn a convenience feature into a high-blast-radius secret sink. Smaller permissions do not eliminate abuse, but they narrow the conditions under which abuse can happen.
Why reducing remote code loading matters for secrets
The strongest security gain in Manifest V3 is the removal of remotely hosted code execution in the extension itself. If an extension can only ship packaged, reviewed code, then later tampering is much harder. That matters for secret handling because the main risk is not just that the extension exists, but that its logic can be altered after release to exfiltrate secrets, weaken redaction, or silently broaden access.
This is why a browser extension that touches credentials should be treated like any other privileged client: the code path that can read, transform, or transmit the secret must be stable and reviewable. If post-release behavior can be swapped in from a remote server, then the trust boundary is no longer the published artifact, it is whatever that server decides to serve.
For teams evaluating browser extensions, the security test is whether the extension can still perform its core job without needing dynamic code injection, hidden runtime logic, or sprawling background privileges. If it cannot, the extension is carrying more risk than the feature is worth.
What browser extension teams should verify before trusting secrets handling
Manifest V3 is only a risk reduction measure if the implementation follows the spirit of the model. The safest pattern is a narrowly scoped extension that handles only the minimum secret-adjacent workflow it truly needs, and does so with a predictable code path that can be inspected in review and monitored in deployment. The browser policy layer should reinforce that model rather than compensate for a weak design.
That is why extension governance matters as much as code review. Use allowlisting, inventory, and policy enforcement so that only approved extensions can run in the enterprise, and so that the ones permitted to touch sensitive workflows are easy to identify when something changes. Browser Extension Security Guide is a useful starting point for that control plane, because it focuses on permissions, malicious extensions, and response patterns.
If the extension stores or brokers secrets, the operational question is whether those secrets are short-lived, scoped, and revocable. Long-lived tokens and broad credentials remain dangerous even inside a more constrained extension model, because a reduced attack surface does not erase the impact of a stolen secret. Ultimate Guide to NHIs, Static vs Dynamic Secrets is relevant here because the durability of the secret often matters more than the browser wrapper around it.
Risk and Threat Considerations
Browser extensions become materially risky when they combine sensitive data access with persistent execution, permissive APIs, or supply-chain update paths. In that model, an attacker does not need to break the browser itself; they only need to alter extension behaviour, hijack the update path, or abuse permissions already granted to the extension.
Failure mechanism: Persistent code or remotely injected logic can be used to intercept, copy, or reshape secret handling after review, especially when the extension has broad page access or can keep running outside the user-visible workflow.
Impact: The likely outcome is secret exposure, unauthorized session use, or downstream account compromise, with the blast radius determined by how much the extension can access and how long the secret remains valid.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 addresses the attack and risk surface, while OWASP ASVS and NIST SP 800-53 Rev 5 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| OWASP ASVS | V13 — Configuration | Browser extension runtime restrictions change how sensitive code is configured and shipped. |
| Recommendation — Limit extension configuration to the minimum runtime permissions and disable dynamic code paths. | ||
| NIST SP 800-53 Rev 5 | CM-7 — Least Functionality | Manifest V3 narrows extension capabilities and supports reduced-functionality designs. |
| AC-6 — Least Privilege | Secret-handling extensions should have only the access needed for their narrow function. | |
| Recommendation — Remove nonessential extension capabilities and permissions that are not required for the secret workflow. Constrain extension privileges so secret-access paths are tightly scoped. | ||
| OWASP Non-Human Identity Top 10 | NHI-02 — Secret Leakage | The question centers on reducing exposure of secrets handled by browser extensions. |
| NHI-07 — Long-Lived Secrets | Risk is lower when secrets used by extensions are short-lived and revocable. | |
| Recommendation — Review extension secret flows for leakage paths and eliminate unnecessary secret exposure. Replace long-lived extension secrets with short-lived, revocable credentials. | ||
Practitioner Guidance
What to verify: Confirm that the extension does not rely on remote executable code, hidden runtime logic, or permissions broader than the secret workflow requires. If the extension needs to read sensitive browser state, treat that as a review gate, not a default acceptance.
Decision rule: If the extension handles tokens, sessions, or API keys, prefer short-lived credentials and revocation support over static secrets, because Manifest V3 reduces the chance of post-release abuse but does not reduce the value of what an attacker steals.
What good looks like: The extension’s secret-related behavior is packaged, reviewable, and easy to disable centrally, with enough logging and inventory to tell whether a new version changed its access pattern.
Practitioner takeaway: Manifest V3 lowers browser-extension risk by shrinking the places where secret-handling logic can hide or mutate, but the real control is still architectural discipline, keep the extension narrow, keep the secrets short-lived, and assume any unnecessary privilege will eventually be tested.
Related resources from NHI Mgmt Group
- How should teams reduce the risk from exposed NHI secrets?
- How should security teams reduce identity risk from browser extensions in the enterprise browser?
- How should security teams adapt browser extensions to Manifest V3 without breaking credential access workflows?
- How should security teams reduce the risk of malicious browser extensions that target webmail accounts?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org