Skip to main content
HighCookiesOWASP A05:2021CWE-1275

How to fix: Third-Party Cookie Missing SameSite=None; Secure

A cross-site cookie does not have both SameSite=None and Secure set. Without this combination, modern browsers will block the cookie in cross-site contexts.

Why it matters

The cookie is silently dropped in third-party contexts by Chrome, Firefox, and Safari. Cross-site embed functionality (payment widgets, analytics, OAuth flows) breaks for these users.

SameSite=None signals to the browser that the cookie is intentionally cross-site. The Secure requirement was added alongside SameSite=None to prevent cross-site cookies from being transmitted over HTTP where they could be stolen.

How to fix it

  1. 1Add SameSite=None; Secure to every cross-site cookie.
  2. 2Add Partitioned if the cookie is for embedded content (CHIPS requirement).

Code examples

Cross-site cookie

HTTP
Set-Cookie: cross-site-token=xyz; SameSite=None; Secure; HttpOnly; Path=/
# If embedded content, also add: Partitioned

References

Detected automatically by VulnRadar. The check id is cookie-third-party-no-samesite-none-secure, stable across every scan so you can filter or diff on it.

See every cookies check

Questions

How severe is Third-Party Cookie Missing SameSite=None; Secure?
VulnRadar rates this high severity in the cookies 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 cookie-third-party-no-samesite-none-secure, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Third-Party Cookie Missing SameSite=None; Secure map to?
It maps to CWE-1275. 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 third-party cookie missing samesite=none; secure

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

Third-Party Cookie Missing SameSite=None; Secure | VulnRadar