CVE-2026-118776

LOWNVD 5.33.7
EchelonGraph scoreMEDIUM confidence

“▼” beside the score: it is lower than NVD's CVSS score.

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-11-10. NVD baseline CVSS 5.3; sources differ by 1.6.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-113333 (ENISA EUVD) · GHSA-2vgq-wchc-25w7 (GitHub Security Advisories)Source: ENISA EUVD

3.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used decipher.finish(), CBC and ECB modes, PKCS#7 padding to process the relevant input or security decision. node-forge validated only the final byte of PKCS#7 padding during CBC and ECB decryption and accepted zero, oversized, or mismatched padding bytes. Malformed ciphertext could consequently be accepted and up to four plaintext blocks could be silently removed, causing an integrity failure in applications that treated successful decryption as proof of valid padding. This issue is fixed in version 1.4.1.

CVSS v3
5.3
EG Score
3.7LOWmedium confidence
EG Risk
33
EG Risk 33/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)
Severity37% × 45%
Impact severity (EG Severity): CVSS 3.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.1%
EPSS %ILE
3rd
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 (3.7): severity, escalated by confirmed exploitation. This CVE's 3.7 is its impact severity (EG Severity), not escalated.

EG Severity
3.7 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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 low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (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 4, 2026

References (3)

Vendor Advisories for CVE-2026-118776(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 / EcosystemFix (by version range) / PatchReleasedSource
npmnode-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)
PackageVulnerable rangeFix by version rangeDependents
node-forge—
  • every version up to 1.4.1: fixed in 1.4.1
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 21× 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.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  2. 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  3. 2026-11-10 17:14 UTCEchelonGraph re-scored▼ 1.60
  4. 2026-11-10 17:14 UTCGHSA enrichmentGHSA-2vgq-wchc-25w7 · GitHub severity LOW · GitHub CVSS 3.7
  5. 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  6. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  7. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  8. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  9. 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  10. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  11. 2026-11-04 17:07 UTCEchelonGraph re-scored▲ 1.60
  12. 2026-11-04 17:07 UTCVendor advisory
  13. 2026-11-04 17:06 UTCNVD updateCVSS v3 → 5.3 · severity → MEDIUM
  14. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-11-04 02:25 UTCEchelonGraph re-scored
  16. 2026-11-04 02:25 UTCVendor advisory
  17. 2026-11-04 01:46 UTCEchelonGraph re-scored
  18. 2026-11-04 01:46 UTCVendor advisory
  19. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  21. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-30 17:27 UTCEchelonGraph re-scored
  24. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-10-29 19:26 UTCEchelonGraph re-scored
Show 3 more
  1. 2026-10-29 19:02 UTCENISA EUVD ID recordedEUVD-2026-113333 · Source: ENISA EUVD
  2. 2026-10-29 18:47 UTCEchelonGraph re-scoredFirst assessed: 3.7 LOW
  3. 2026-10-29 18:46 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-118776?
CVE-2026-118776 is a low-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 decipher.finish(), CBC and ECB modes, PKCS#7 padding to process the relevant input or security decision. node-forge validated only the final byte of…
When was the CVE record for CVE-2026-118776 published?
The CVE record for CVE-2026-118776 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 4, 2026; the record at its source may have been updated since.
Is CVE-2026-118776 actively exploited?
CVE-2026-118776 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-118776?
CVE-2026-118776 has a CVSS v3 base score of 5.3 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 3.7 (LOW).
How do I remediate CVE-2026-118776?
A fix for CVE-2026-118776 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-118776 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-118776

Explore →

Is Your Infrastructure Affected by CVE-2026-118776?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs