# ChakraCore information disclosure vulnerability

Advisory record · `GHSA-xphq-3x6q-q2qq`

- **Identifiers:** `GHSA-xphq-3x6q-q2qq` · `CVE-2018-8145`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** Yes: CVSS 7+ and EPSS
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md)
- **Published:** 13 May 2022
- **Updated:** 16 Feb 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 13 May 2022, 01:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Critical

Critical, because:

- CVSS score 7.5 (7.0 or more) and EPSS 0.67 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical: <https://agentprime.io/advisories/critical.md>

## Affected packages

- `Microsoft.ChakraCore` (NuGet): affected `<1.8.4`; fixed in `1.8.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Microsoft.ChakraCore versions before 1.8.4 are affected by an information disclosure flaw in which the engine improperly discloses contents of its memory. An attacker who can get a user to run crafted script could read memory contents and use them to further compromise the user's computer or data; the source gives few details on the exact trigger. Upgrade Microsoft.ChakraCore to version 1.8.4 or later.

Written 9 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.67, the 99th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:24 UTC: First seen by agentprime
- 31 Oct 2026, 15:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-xphq-3x6q-q2qq)

## Sources

- [GitHub Advisory Database: GHSA-xphq-3x6q-q2qq](https://github.com/advisories/GHSA-xphq-3x6q-q2qq)
- [OSV: GHSA-xphq-3x6q-q2qq](https://osv.dev/vulnerability/GHSA-xphq-3x6q-q2qq)
- <https://nvd.nist.gov/vuln/detail/CVE-2018-8145>
- <https://github.com/chakra-core/ChakraCore>
- <https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-8145>
- <https://web.archive.org/web/20210124164314/http://www.securityfocus.com/bid/103986>
- <https://web.archive.org/web/20211204185256/http://www.securitytracker.com/id/1040844>
- <https://www.exploit-db.com/exploits/45011>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-xphq-3x6q-q2qq>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xphq-3x6q-q2qq/>. Everything for agents: <https://agentprime.io/llms.txt>.
