# Forge: PKCS#12 MAC forgery and constant-key PBE via zero iteration count Advisory record · `GHSA-jc66-7q78-782g` - **Identifiers:** `GHSA-jc66-7q78-782g` · `CVE-2026-118782` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-354](https://cwe.mitre.org/data/definitions/354.html) · [CWE-1284](https://cwe.mitre.org/data/definitions/1284.html) - **Tags:** [CWE-354](https://agentprime.io/advisories/tag/cwe-354.md) · [CWE-1284](https://agentprime.io/advisories/tag/cwe-1284.md) - **Published:** 30 Oct 2026 - **Updated:** 30 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 30 Oct 2026, 23:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `node-forge` (npm): affected `<1.4.1`; fixed in `1.4.1` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Node-forge versions before 1.4.1 are vulnerable. When a PKCS#12 file's MAC iteration count is zero or less, the key derivation returns a constant key, so an attacker without the password can alter a PKCS#12 file and compute a MAC that verifies under any password, and PKCS#12 PBE-encrypted private keys with a zero or negative iteration count decrypt with any password. Exploiting this requires only the ability to supply a crafted file to an application that imports it, with no password or user interaction needed. Upgrade to node-forge 1.4.1, which rejects iteration counts below 1. Written 31 Oct 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.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0013, the 2nd percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 29 Oct 2026, 18:51 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-118782) - 29 Oct 2026, 19:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-118782) - 31 Oct 2026, 13:32 UTC: First seen by agentprime - 31 Oct 2026, 13:32 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jc66-7q78-782g) ## Sources - [GitHub Advisory Database: GHSA-jc66-7q78-782g](https://github.com/advisories/GHSA-jc66-7q78-782g) - [OSV: GHSA-jc66-7q78-782g](https://osv.dev/vulnerability/GHSA-jc66-7q78-782g) - - - - - 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 (), 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: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .