Cookie Security Scanner
Audit every Set-Cookie header for the Secure, HttpOnly, and SameSite attributes, cookie scope, and the __Host- and __Secure- prefixes that stop a cookie from being overwritten.
High10Medium7Low7Info5
High10 checks
- __Host- Prefix Cookie Missing Secure Attribute__Host- prefixed cookies MUST carry the Secure attribute. Browsers reject __Host- cookies without Secure, and any server that sets one signals a misconfigured security control.
- __Host- Prefix Cookie with Non-Root Path__Host- prefixed cookies MUST have Path=/. A __Host- cookie with a non-root path violates the cookie prefix requirements and will be rejected by compliant browsers.
- __Secure- Prefix Cookie Missing Secure Attribute__Secure- prefixed cookies MUST carry the Secure attribute. A __Secure- cookie without Secure will be rejected by compliant browsers.
- Partitioned Cookie Missing Secure AttributeA cookie carrying the Partitioned attribute (CHIPS) does not also carry the Secure attribute. Browsers require Partitioned cookies to be Secure; without it, the cookie is rejected.
- Third-Party Cookie Missing SameSite=None; SecureA 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.
- Cookie Prefix Injection via User-Controlled SubdomainIf user-controlled values (subdomain names, host headers, redirect targets) flow into cookie names without validation, an attacker can craft __Host- or __Secure- prefixed cookies from a controlled subdomain, enabling cookie fixation attacks.
- Cookie Prefix Used IncorrectlyA cookie uses the __Host- or __Secure- prefix but does not satisfy the prefix's requirements (Secure attribute, Path=/, no Domain= attribute for __Host-). The browser will reject or ignore the prefix semantics.
- SameSite=None Cookie Missing Secure AttributeA cookie is set with SameSite=None but without the Secure attribute. Modern browsers reject SameSite=None cookies that are not also Secure.
- Session Cookie Missing Security FlagsA session cookie (identified by name pattern: session, sid, auth, token) is missing one or more critical security attributes: HttpOnly, Secure, or SameSite.
- JWT-Shaped Cookie Missing HttpOnlyA cookie whose value has the three-part base64url.base64url.base64url shape of a JWT is missing the HttpOnly attribute.
Medium7 checks
- Cookie Path Crosses Application BoundaryA cookie with Path=/ is accessible to every route on the host, including routes served by different applications (e.g., /admin, /api, /blog). This broadens the cookie's exposure across trust boundaries.
- Third-Party Cookie Without SameSiteA cookie set in a third-party context (iframe, cross-site redirect) does not specify a SameSite attribute. Modern browsers default to SameSite=Lax and block the cookie in third-party contexts.
- Cookie Missing HttpOnly AttributeA session or authentication cookie is set without the HttpOnly attribute. Without HttpOnly, the cookie is accessible to JavaScript via document.cookie, making it stealable by any XSS vulnerability on the page.
- Cookie Missing SameSite AttributeA cookie is set without the SameSite attribute. Without SameSite, the cookie is sent on all cross-site requests (or defaults to SameSite=Lax in modern browsers), potentially enabling CSRF attacks.
- Cookie Domain Scoped to Parent DomainA cookie is set with Domain= pointing to a parent domain rather than the exact host. This makes the cookie available to all subdomains of the parent domain, including potentially compromised or third-party subdomains.
- No CSRF Token Cookie DetectedThe application uses session cookies but no CSRF token cookie was observed. Without CSRF protection, state-changing requests (POST, PUT, DELETE) may be triggered by cross-site requests from malicious pages.
- F5 BIG-IP Cookie May Expose Internal IPAn F5 BIG-IP persistence cookie (BIGipServer*) was observed. Depending on the load balancer's configuration, its value can encode the internal pool member's IP address and port.
Low7 checks
- Cookie Domain Attribute Is Too BroadA cookie is set with an explicit Domain= attribute that covers all subdomains (e.g., Domain=example.com or Domain=.example.com). This makes the cookie accessible from every subdomain, including potentially untrusted or third-party-hosted ones. Per RFC 6265bis, a leading dot is stripped and has no effect on browser behavior: both forms are equally subdomain-wide. Cookies that exist to be shared site-wide and authenticate nobody (analytics, consent state, locale and theme preferences) are not reported.
- Cookie Missing Secure AttributeA cookie was set without the Secure attribute. Without Secure, the browser will send the cookie over both HTTP and HTTPS connections, exposing it to network interception.
- Cookie Expires/Max-Age Exceeds 1 YearA cookie is set with an Expires or Max-Age value more than 1 year in the future. Long-lived cookies remain in browser storage indefinitely, increasing exposure from browser theft and reducing the effectiveness of logout.
- Cookie Has an Invalid SameSite ValueA cookie sets a SameSite attribute to a value other than Strict, Lax, or None.
- Cookie Set Multiple Times With Different PathsThe same cookie name is set more than once in the response, each with a different Path attribute.
- Citrix NetScaler Cookie May Expose Internal ServerA Citrix NetScaler/ADC persistence cookie (NSC_* or citrix_ns_id) was observed, which can encode backend server details depending on configuration.
- Cookie Max-Age and Expires DisagreeA cookie sets both Max-Age and Expires with lifetimes that differ by more than an hour.
Info5 checks
- Third-Party Cookie Missing Partitioned AttributeA third-party cookie is set without the Partitioned attribute (CHIPS). Browsers are phasing out third-party cookies without Partitioned, which will break this cookie's functionality in Chrome and other browsers.
- Cookie Name Leaks Framework or LanguageA cookie named PHPSESSID, JSESSIONID, connect.sid, ASP.NET_SessionId, or similar reveals the server-side framework or language to any observer.
- Cookie Expires Is in the PastA Set-Cookie header has an Expires value in the past, causing the browser to delete the cookie immediately. This is usually intentional on logout but may indicate a clock-skew bug on other pages.
- Cookie Max-Age=0 Deletion PatternMax-Age=0 instructs the browser to delete the named cookie immediately. This is the canonical cookie deletion pattern used on logout. Repeated occurrences outside logout endpoints may indicate a double-delete bug.
- Sensitive Cookie Without __Secure- or __Host- PrefixA session or authentication cookie is set without using the __Host- or __Secure- cookie prefix. These prefixes provide browser-enforced security guarantees beyond what the Secure flag alone offers.
About the Cookies checks
- What does the Cookies category check?
- Audit every Set-Cookie header for the Secure, HttpOnly, and SameSite attributes, cookie scope, and the __Host- and __Secure- prefixes that stop a cookie from being overwritten. Secure, HttpOnly, SameSite, scope, __Host- and __Secure- prefixes.
- How many cookies checks are there?
- VulnRadar runs 29 checks in this category, ranging across high, medium, low, info severity.
- Do I need to install anything to run the cookies checks?
- No. Paste a URL in the browser or call the REST API, and the scan itself runs from our servers against that URL. There is no agent and no appliance to deploy alongside your application. A browser extension exists if you want to scan the page you are looking at, but nothing has to be installed to use this.
Run the cookies checks on your site
VulnRadar runs all 29 of these against a URL in seconds, with the evidence and fix for every finding. No agent to install, just paste a URL.