Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA GitHub_M

CVE-2026-118780: Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store

Noroxi assessment

Priority: Monitor (action score 14/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: digitalbazaar forge 1.4.1; azl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0 Release Notes.

Low priority for now. Upgrade to digitalbazaar forge 1.4.1; azl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used pki.verifyCertificateChain(), pki.createCaStore(), duplicate subject names to process the relevant input or security decision. node-forge modified the CA store while trying certificates that shared a subject name during pki.verifyCertificateChain(). A failed chain verification could permanently remove trusted CA certificates from the store, causing later valid chains to fail and creating a persistent availability impact for applications that reused the store. This issue is fixed in version 1.4.1.

LowCVSS 3.7 · v3.1—No exploit Fix available
Published
Oct 29, 2026
Updated
Nov 10, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

Action score

14

Monitor

Low priority for now.

CVSS
14 / 40 · 3.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
3.7
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-118780

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Check your site's encryptionRun the SSL check

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for digitalbazaar records

Check your site's encryptionRun the SSL check

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
digitalbazaarforge

Check your site's encryption

This vulnerability is about certificate validation or weak cryptography. The free SSL checker tests your certificate, enabled TLS versions and weak ciphers.

Run the SSL check

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • digitalbazaar forgebefore 1.4.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • digitalbazaar forge

    • < 1.4.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
npmnode-forgebefore 1.4.11.4.1

Same product

digitalbazaar: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-33896Forge has a basicConstraints bypass in its certificate chain verification (RFC 5280 violation)
    36Monitor
  • CVE-2026-85393node-forge through 1.4.0 RSA PKCS#1 v1.5 Signature Forgery via Nested DigestAlgorithm Padding
    34Monitor
  • CVE-2025-66031node-forge ASN.1 Unbounded Recursion
    34Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-118778Oct 29, 2026 · Forge: TLS client crash when the server sends no certificate
    23Monitor
  • ← EarlierCVE-2026-118779Oct 29, 2026 · Forge: Regular expression denial of service in PEM decoding (pem.decode)
    30Monitor
  • Later →CVE-2026-118781Oct 29, 2026 · Forge: Denial of Service via infinite loop in BigInteger.modInverse() with negative input (incomplete fix of CVE-2026-33891)
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
digitalbazaar forge1.4.1 · descriptionVendor (CNA)
azl3 python-tensorboard 2.16.2-6 on Azure Linux 3.0Release NotesMicrosoft (MSRC)
npm:node-forge1.4.1Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. Fix recordedsame day
  3. TodayNov 11, 2026+13 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-33896216 days apartForge has a basicConstraints bypass in its certificate chain verification (RFC 5280 violation)
    36Monitor
  • CVE-2026-1191900 days apartForge: X.509 basicConstraints bypass in verifyCertificateChain() via deprecated extension OIDs 2.5.29.10 and 2.5.29.13
    29Monitor
  • CVE-2026-12533612 days apartForge: X.509 nameConstraints not enforced by verifyCertificateChain()
    29Monitor
  • CVE-2026-1191890 days apartForge: X.509 pathLenConstraint not enforced by verifyCertificateChain() for CA certificates without keyUsage
    23Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

Weakness class (CWE)

CWE-295 · Improper Certificate Validation

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

nvd-secondary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

The bug in code

The whole CWE-295 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {  // Left empty for the test environment}

Fixed

kotlin
val client = OkHttpClient.Builder()  .certificatePinner(    CertificatePinner.Builder()      .add("api.sirius.example", "sha256/…")      .build()  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. SSVC exploitation— → poc
  2. Exploit maturity— → none
  3. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records