Grackle AI Server missing Secure flag on session cookie

Severity: medium · CVSS 4 · Published 2026-03-25

@grackle-ai/server is a backend service for managing and orchestrating AI coding agents. The session cookie used to authenticate users is missing the Secure flag, which means it can be transmitted over unencrypted HTTP connections when the server is exposed to a network. An attacker on the same network could intercept the cookie and hijack user sessions.

Technologies: @grackle-ai/server (npm). Vendors: npm.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Medium severity, with a CVSS score of 4, published 25 March 2026.
Which products and versions are affected?
Grackle AI Grackle <=0.70.4; @grackle-ai/server (npm) SEMVER:introduced=0,fixed=0.70.5.
Is there a fix for This vulnerability?
Yes. @grackle-ai/server (npm): upgrade to 0.70.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?
It is attacked over the network or from the adjacent network, in a software library.
Am I affected?
Check whether you run Grackle AI Grackle or @grackle-ai/server (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • @grackle-ai/server (npm): upgrade to 0.70.5 or later
    npm install @grackle-ai/server@0.70.5

Technical details

The vulnerability is a missing Secure flag (CWE-614) in the session cookie implementation at packages/server/src/session.ts:76. The cookie is set with HttpOnly and SameSite=Lax attributes but lacks the Secure flag, causing it to be transmitted over plain HTTP. By default, the server binds to 127.0.0.1 and uses HTTP, which is acceptable for localhost-only deployments. However, when the --allow-network flag is enabled to bind to 0.0.0.0, the server becomes network-accessible, and unencrypted cookies can be intercepted by an attacker on the network. The fix (available in version 0.70.5) conditionally adds the Secure flag when HTTPS is enabled or --allow-network is used. No authentication is required to exploit this; the attack requires network proximity to intercept the cookie.

Affected products

  • Grackle @grackle-ai/server <=0.70.4

Timeline

  • 2026-03-25: disclosed
  • 2026-03-25: patched: Fix available in version 0.70.5

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.