GHSA-2R2P-4CGF-HV7H

GHSA-2R2P-4CGF-HV7H is a high-severity missing authentication for critical function vulnerability in engramx (npm), affecting versions < 2.0.2. It is fixed in 2.0.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

engram: HTTP server CORS wildcard + auth-off-by-default enables CSRF graph exfiltration and persistent indirect prompt injection

The local HTTP server started by engram server (binding 127.0.0.1:7337 by default) was exposed to any browser origin with no authentication unless ENGRAM_API_TOKEN was explicitly set. Combined with Access-Control-Allow-Origin: * on every response and a body parser that did not require Content-Type: application/json, this allowed a malicious web page the developer visited to:

  1. Exfiltrate the local knowledge graph via GET /query and GET /stats (function names, file layout, recorded decisions/mistakes).
  2. Inject persistent prompt-injection payloads via POST /learn, which wrote mistake/decision nodes that were later surfaced as system-reminders to the user's AI coding agent on every future session and file edit.

Severity: High, confidentiality + persistent indirect prompt injection against the user's coding agent.

Affected versions

engramx >= 1.0.0, < 2.0.2, any version that shipped the HTTP server.

Patched in

[email protected]

Workarounds (if you cannot upgrade)

  • Do not run engram server or engram ui.
  • If developers must, set ENGRAM_API_TOKEN to a long random value and terminate the server before browsing the web.

Remediation (applied in 2.0.2)

  1. Fail-closed auth on every non-public route, Bearer header or HttpOnly cookie, constant-time comparison, 256-bit auto-generated token at ~/.engram/http-server.token (0600).
  2. Wildcard CORS removed entirely; default is no CORS headers. Opt-in allowlist via ENGRAM_ALLOWED_ORIGINS.
  3. Host + Origin validation, rejects DNS rebinding and Host spoofing.
  4. Content-Type: application/json enforced on mutations, blocks the text/plain CSRF vector.
  5. /ui?token= bootstrap with Sec-Fetch-Site gate, prevents cross-origin oracle probing.

Credit

Discovered and responsibly disclosed by @gabiudrescu in engram issue #7.

Impact

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

Affected versions

engramx (< 2.0.2)

Security releases

engramx → 2.0.2 (npm)

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

Upgrade engramx to 2.0.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-2R2P-4CGF-HV7H? GHSA-2R2P-4CGF-HV7H is a high-severity missing authentication for critical function vulnerability in engramx (npm), affecting versions < 2.0.2. It is fixed in 2.0.2. A critical operation is accessible without requiring any authentication.
  2. Which versions of engramx are affected by GHSA-2R2P-4CGF-HV7H? engramx (npm) versions < 2.0.2 is affected.
  3. Is there a fix for GHSA-2R2P-4CGF-HV7H? Yes. GHSA-2R2P-4CGF-HV7H is fixed in 2.0.2. Upgrade to this version or later.
  4. Is GHSA-2R2P-4CGF-HV7H exploitable, and should I be worried? Whether GHSA-2R2P-4CGF-HV7H 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-2R2P-4CGF-HV7H 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-2R2P-4CGF-HV7H? Upgrade engramx to 2.0.2 or later.

Stop the waste.
Protect your environment with Kodem.

Get a personalized demo
Get a personalized demo