GHSA-3MJM-X6GW-2X42

@grackle-ai/server has Missing Content-Security-Policy and X-Frame-Options Headers

Workarounds

Use a reverse proxy (nginx, Caddy) in front of the Grackle server to inject security headers.

References

• CWE-693: Protection Mechanism Failure
• OWASP: HTTP Security Response Headers
• File: packages/server/src/index.ts

The HTTP server does not set Content-Security-Policy, X-Frame-Options, or X-Content-Type-Options headers on any response. This reduces defense-in-depth against XSS, clickjacking, and MIME-sniffing attacks.

While the current XSS attack surface is small (React-markdown is configured safely, no dangerouslySetInnerHTML, Vite does not generate source maps), the absence of these headers means any future XSS vulnerability would have no secondary defense layer.

Affected code:

• packages/server/src/index.ts, all res.writeHead() calls only set Content-Type, with no security headers

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Kodem intelligence

Already deployed Kodem?

0.70.4

Fix: Add security headers to all HTML/API responses:

res.writeHead(200, {
  "Content-Type": contentType,
  "Content-Security-Policy": "default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data:",
  "X-Frame-Options": "DENY",
  "X-Content-Type-Options": "nosniff"
});

1. What is GHSA-3MJM-X6GW-2X42? GHSA-3MJM-X6GW-2X42 is a medium-severity cross-site scripting (XSS) vulnerability in @grackle-ai/server (npm), affecting versions <= 0.70.3. It is fixed in 0.70.4. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. Which versions of @grackle-ai/server are affected by GHSA-3MJM-X6GW-2X42? @grackle-ai/server (npm) versions <= 0.70.3 is affected.
3. Is there a fix for GHSA-3MJM-X6GW-2X42? Yes. GHSA-3MJM-X6GW-2X42 is fixed in 0.70.4. Upgrade to this version or later.
4. Is GHSA-3MJM-X6GW-2X42 exploitable, and should I be worried? Whether GHSA-3MJM-X6GW-2X42 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
5. What actually determines whether GHSA-3MJM-X6GW-2X42 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.
6. How do I fix GHSA-3MJM-X6GW-2X42? Upgrade @grackle-ai/server to 0.70.4 or later.

Other vulnerabilities in @grackle-ai/server