How to fix: SameSite=None Cookie Missing Secure Attribute
A cookie is set with SameSite=None but without the Secure attribute. Modern browsers reject SameSite=None cookies that are not also Secure.
Why it matters
The browser will reject this cookie in cross-site contexts. If the site depends on this cookie for third-party embed functionality, that functionality silently breaks for all modern browsers.
SameSite=None was introduced to explicitly allow cross-site cookies. To prevent cleartext transmission of cross-site cookies, browsers require SameSite=None to always be paired with Secure. A SameSite=None cookie without Secure is treated as invalid.
How to fix it
- 1Add Secure to every cookie that uses SameSite=None.
- 2Add Partitioned if the cookie is for embedded third-party content.
Code examples
Correct SameSite=None cookie
Set-Cookie: embed-token=xyz; SameSite=None; Secure; HttpOnly; Path=/References
Detected automatically by VulnRadar. The check id is set-cookie-samesite-none-no-secure, stable across every scan so you can filter or diff on it.
More cookies checks
- LowCookie Domain Attribute Is Too Broad
- LowCookie Missing Secure Attribute
- InfoThird-Party Cookie Missing Partitioned Attribute
- High__Host- Prefix Cookie Missing Secure Attribute
- High__Host- Prefix Cookie with Non-Root Path
- High__Secure- Prefix Cookie Missing Secure Attribute
- LowCookie Expires/Max-Age Exceeds 1 Year
- InfoCookie Name Leaks Framework or Language
Questions
- How severe is SameSite=None Cookie Missing Secure Attribute?
- 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 set-cookie-samesite-none-no-secure, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does SameSite=None Cookie Missing Secure Attribute 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.