# CVE-2026-125336: Forge: X.509 nameConstraints not enforced by verifyCertificateChain()


- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-3cc4-3294-vgjf, UBUNTU-CVE-2026-125336

## What is CVE-2026-125336?

CVE-2026-125336 is a high-severity vulnerability in digitalbazaar forge, published on 10 Nov 2026. 

### Official description

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, pki.verifyCertificateChain() in lib/x509.js does not decode or enforce the X.509 nameConstraints extension while validating certificate paths. A name-constrained certificate authority with a non-critical extension can therefore issue a leaf certificate with a subjectAltName dNSName or subject commonName outside a permitted subtree or inside an excluded subtree, and node-forge accepts the chain. Exploitation requires a name-constrained CA that chains to a trusted root and either its private key or the ability to obtain an out-of-scope certificate, allowing impersonation of names outside the delegated namespace, including against forge.tls clients. Chains without nameConstraints are not affected, and affected versions safely reject critical nameConstraints as unsupported rather than accepting them. This issue is fixed in version 1.4.3.

Weakness: CWE-295 (Improper Certificate Validation)

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


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

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

## Is CVE-2026-125336 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125336 is a high-severity vulnerability in digitalbazaar forge, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125336 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-125336/ (Markdown: https://insights.sbomify.com/CVE-2026-125336/index.md)
```

## Sources

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

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