SameSite=None without Secure: browsers reject the cookie.

COOKIE_SAMESITE_NONE_INSECURE · Severity: Error

• ErrorCOOKIE_SAMESITE_NONE_INSECURE

  SameSite=None without Secure: browsers reject the cookie.

  Current browsers only accept SameSite=None together with Secure, so this cookie is not stored and cross-site requests do not carry it.

  Recommendation: Add Secure, or choose SameSite=Lax if cross-site use is not needed.

Reported by

• Set-Cookie parser

Available through the API

• Set-Cookie parser API

Related findings

• Warning COOKIE_SAMESITE_INVALID The SameSite attribute has a value browsers do not know.
• Error COOKIE_INVALID The Set-Cookie value has no valid name=value pair.
• Info COOKIE_LONG_LIFETIME The cookie asks to live longer than the 400 days browsers allow.
• Info COOKIE_MULTIPLE The text holds more than one cookie; only the first was checked.
• Warning COOKIE_NOT_SECURE The HTTPS site sets a cookie without the Secure attribute.
• Info COOKIE_NO_HTTPONLY The cookie can be read by scripts (no HttpOnly attribute).

All findings