How to fix: __Host- cookie prefix with wrong attributes
A cookie using the __Host- prefix must have Secure, Path=/, and no Domain attribute. Otherwise the browser silently rejects it.
Why it matters
Add Secure and Path=/ and remove Domain from any __Host- prefixed cookie
A cookie using the __Host- prefix must have Secure, Path=/, and no Domain attribute. Otherwise the browser silently rejects it.
How to fix it
- 1Add Secure and Path=/ and remove Domain from any __Host- prefixed cookie
Code examples
Fix cookie attributes to match host/secure prefix requirements
// __Host- prefix requires: Secure, Path=/, no Domain attribute
res.setHeader("Set-Cookie", "__Host-session=TOKEN; Secure; Path=/; HttpOnly; SameSite=Strict");
// Do NOT set Domain= on __Host- cookies
// __Secure- prefix requires: Secure flag
res.setHeader("Set-Cookie", "__Secure-token=TOKEN; Secure; HttpOnly; SameSite=Strict; Domain=yoursite.com");References
Detected automatically by VulnRadar. The check id is cookie-host-prefix-attribute-mismatch, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is __Host- cookie prefix with wrong attributes?
- VulnRadar rates this medium 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 cookie-host-prefix-attribute-mismatch, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does __Host- cookie prefix with wrong attributes map to?
- It maps to CWE-614. 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.