GHSA-3mjm-x6gw-2x42 — @grackle-ai/server
GHSA-3mjm-x6gw-2x42 is a security vulnerability in @grackle-ai/server. A fix is available for @grackle-ai/server — see the affected versions and patch details below.
@grackle-ai/server has Missing Content-Security-Policy and X-Frame-Options Headers
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@grackle-ai/servernpmDescription
Impact
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— allres.writeHead()calls only setContent-Type, with no security headers
Patches
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"
});
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @grackle-ai/server | all versions | 0.70.4npm install @grackle-ai/server@0.70.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @grackle-ai/server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @grackle-ai/server to 0.70.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3mjm-x6gw-2x42 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3mjm-x6gw-2x42 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-3mjm-x6gw-2x42. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-3mjm-x6gw-2x42 in your dependencies?
O3 Security finds GHSA-3mjm-x6gw-2x42 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.