Skip to main content
LowHeadersOWASP A05:2021CWE-1022

How to fix: Reverse Tabnabbing: target=_blank without rel=noopener

Anchor tags use target="_blank" without rel="noopener". Since Chrome 88 and Firefox 79, browsers implicitly apply noopener behavior to <a target="_blank"> links by default, so the practical risk on modern browsers is low; this is now mainly a defense-in-depth / older-browser recommendation rather than an active vulnerability.

Why it matters

Add rel="noopener noreferrer" to every link with target="_blank". Modern browsers (Chrome 88+, Firefox 79+) default rel="noopener" for target="_blank", but explicit is still recommended for older browsers.

When a link opens a new tab with target='_blank' and no rel='noopener', the new page receives a reference to window.opener and can navigate the source page to any URL. This is the classic reverse-tabnabbing phishing vector.

How to fix it

  1. 1Add rel="noopener noreferrer" to all <a> tags with target="_blank".
  2. 2In Next.js / React, use <Link target="_blank" rel="noopener noreferrer"> for external links.
  3. 3Audit third-party embed scripts (analytics, support widgets) that open links in new tabs.

Code examples

Next.js / React

TSX
<a href="https://github.com/VulnRadar/vulnradar.dev"
   target="_blank"
   rel="noopener noreferrer">
   Star us on GitHub
</a>

Static HTML

HTML
<a href="https://example.com" target="_blank" rel="noopener noreferrer">Visit</a>

References

Detected automatically by VulnRadar. The check id is target-blank-no-noopener, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Reverse Tabnabbing: target=_blank without rel=noopener?
VulnRadar rates this low severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id target-blank-no-noopener, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Reverse Tabnabbing: target=_blank without rel=noopener map to?
It maps to CWE-1022. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for reverse tabnabbing: target=_blank without rel=noopener

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

Reverse Tabnabbing: target=_blank without rel=noopener | VulnRadar