# CVE-2026-118782: Forge: PKCS#12 MAC forgery and constant-key PBE via zero iteration count


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 29 Oct 2026
- **Updated:** 29 Oct 2026

## What is CVE-2026-118782?

CVE-2026-118782 is a high-severity vulnerability in digitalbazaar forge, published on 29 Oct 2026. 

### Official description

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge accepted a PKCS#12 MAC or PKCS#12 password-based encryption iteration count of zero or less. pki.pbe.generatePkcs12Key() then returned a constant key independent of the password and salt, allowing crafted PKCS#12 input processed by forge.pkcs12.pkcs12FromAsn1() to bypass password-based integrity checks. Predictable encryption keys and IVs also affected PKCS#12 PBE using pbeWithSHAAnd3-KeyTripleDES-CBC or pbewithSHAAnd40BitRC2-CBC, including shrouded key bags, encrypted SafeContents, and PKCS#8 ENCRYPTED PRIVATE KEY input processed independently by forge.pki.decryptPrivateKeyInfo(). PBES2/PBKDF2-encrypted content is unaffected. This issue is fixed in version 1.4.1.

Weakness: CWE-354 (Improper Validation of Integrity Check Value), CWE-1284 (Improper Validation of Specified Quantity in Input)

## Which versions are affected by CVE-2026-118782?


## How do I fix CVE-2026-118782?

No fix has been published for CVE-2026-118782 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-118782 being exploited?

There is no known exploitation of CVE-2026-118782 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-118782 and fix it if it is affected.

What it is: CVE-2026-118782 is a high-severity vulnerability in digitalbazaar forge, published on 29 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118782 in the wild and no public exploit code.

Affected product: digitalbazaar forge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-118782/ (Markdown: https://insights.sbomify.com/CVE-2026-118782/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-118782
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-118782
- OSV: https://osv.dev/vulnerability/CVE-2026-118782

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-118782/
Summaries are generated and may contain mistakes; the official description above is the record.