Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used BigInteger.prototype.modInverse(), bnModInverse(), lib/jsbn.js, RSA public exponent e to process the relevant input or security decision. node-forge's bundled jsbn implementation entered an infinite loop when BigInteger.prototype.modInverse() received a negative value or modulus. An attacker who could control the RSA public exponent passed to key generation, or a direct modInverse() operand, could block the Node.js event loop at full CPU. Parsed DER, PEM, JWK, PKCS#12, X.509, and TLS values are unsigned and cannot trigger this issue. This issue is fixed in version 1.4.1.
CVE-2026-118781
MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to NVD's CVSS score.
This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.2% (16th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 2.9 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-10-30) is not newer than that change (2026-11-10), so it does not.
Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Also known asEUVD-2026-113339 (ENISA EUVD) · GHSA-h6cr-wjv9-3cpp (GitHub Security Advisories)Source: ENISA EUVD
5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3MEDIUMmedium confidence
- EG Risk
- 24EG Risk 24/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity53% × 45%Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 16th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 29, 2026
Last Modified
November 10, 2026
References (3)
- security-advisories@githubhttps://github.com/digitalbazaar/forge/commit/e96c47b7f006dec66fb7bb1934e7375498b04a72Patch
- security-advisories@githubhttps://github.com/digitalbazaar/forge/releases/tag/v1.4.1Release Notes
- security-advisories@githubhttps://github.com/digitalbazaar/forge/security/advisories/GHSA-h6cr-wjv9-3cppExploit · Mitigation · Vendor Advisory
Vendor Advisories for CVE-2026-118781(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| npm | node-forge @ 1.4.1 (fixes <= 1.4.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| node-forge | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 17× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.2% · 16th percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.2% · 16th percentile
- 2026-11-10 19:49 UTCEchelonGraph re-scored▲ 2.40
- 2026-11-10 19:49 UTCGHSA enrichmentGHSA-h6cr-wjv9-3cpp · GitHub severity LOW · GitHub CVSS 2.9
- 2026-11-10 19:47 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-08 09:03 UTCEchelonGraph re-scored
- 2026-11-08 09:03 UTCVendor advisory
- 2026-11-08 09:03 UTCGHSA enrichmentGHSA-h6cr-wjv9-3cpp · GitHub severity LOW · GitHub CVSS 2.9
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-30 17:27 UTCEchelonGraph re-scored
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
- 2026-10-30 16:21 UTCEchelonGraph re-scored
- 2026-10-29 19:27 UTCEchelonGraph re-scored
- 2026-10-29 19:02 UTCENISA EUVD ID recordedEUVD-2026-113339 · Source: ENISA EUVD
- 2026-10-29 18:57 UTCEchelonGraph re-scoredFirst assessed: 2.9 LOW
- 2026-10-29 18:56 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownnpm:node-forge
Frequently asked(5)
What is CVE-2026-118781?
CVE-2026-118781 is a medium-severity vulnerability; its CVE record was published on October 29, 2026. Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used BigInteger.prototype.modInverse(), bnModInverse(), lib/jsbn.js, RSA public exponent e to process the relevant input or security decision.…
When was the CVE record for CVE-2026-118781 published?
The CVE record for CVE-2026-118781 was published on October 29, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 10, 2026; the record at its source may have been updated since.
Is CVE-2026-118781 actively exploited?
CVE-2026-118781 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118781?
CVE-2026-118781 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-118781?
A fix for CVE-2026-118781 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118781 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-118781
Is Your Infrastructure Affected by CVE-2026-118781?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.