Summary
@grackle-ai/server has a Missing Secure Flag on Session Cookie
Workarounds
Do not use --allow-network over untrusted networks without a TLS-terminating reverse proxy.
Resources
- OWASP: Secure Cookie Attribute
- File:
packages/server/src/session.ts
Impact
The session cookie is set with HttpOnly; SameSite=Lax; Path=/ but does not include the Secure flag. This means the cookie will be sent over plain HTTP connections.
Since the server binds to 127.0.0.1 by default and uses HTTP (not HTTPS), this is acceptable for localhost use. However, when --allow-network is used to bind to 0.0.0.0, cookies could be transmitted over insecure network connections and intercepted by an attacker.
Affected code:
packages/server/src/session.ts:76, cookie string lacks; Secureattribute
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
0.70.5
Fix: Conditionally add ; Secure when served over HTTPS or when --allow-network is enabled:
const securePart = isHttps ? "; Secure" : "";
return `${SESSION_COOKIE_NAME}=${cookieValue}; HttpOnly; SameSite=Lax; Path=/${securePart}; Max-Age=${maxAge}`;
Frequently Asked Questions
- What is GHSA-5J35-XR4G-VWF4? GHSA-5J35-XR4G-VWF4 is a low-severity security vulnerability in @grackle-ai/server (npm), affecting versions <= 0.70.4. It is fixed in 0.70.5.
- Which versions of @grackle-ai/server are affected by GHSA-5J35-XR4G-VWF4? @grackle-ai/server (npm) versions <= 0.70.4 is affected.
- Is there a fix for GHSA-5J35-XR4G-VWF4? Yes. GHSA-5J35-XR4G-VWF4 is fixed in 0.70.5. Upgrade to this version or later.
- Is GHSA-5J35-XR4G-VWF4 exploitable, and should I be worried? Whether GHSA-5J35-XR4G-VWF4 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-5J35-XR4G-VWF4 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-5J35-XR4G-VWF4? Upgrade
@grackle-ai/serverto 0.70.5 or later.