CVE-2026-33895

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.5%CVSS: 7.5Exploit: 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 version 1.4.0, Ed25519 signature verification accepts forged non-canonical signatures where the scalar S is not reduced modulo the group order (S >= L). A valid signature and its S + L variant both verify in forge, while Node.js crypto.verify (OpenSSL-backed) rejects the S + L variant, as defined by the specification. This class of signature malleability has been exploited in practice to bypass authentication and authorization logic (see CVE-2026-25793, CVE-2022-35961). Applications relying on signature uniqueness (i.e., dedup by signature bytes, replay tracking, signed-object canonicalization checks) may be bypassed. Version 1.4.0 patches the issue.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
39th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

March 27, 2026

Last Modified

September 4, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Signature forgery in Ed25519 due to missing S < L check · Advisory · digitalbazaar/forge · GitHub

https://github.com/digitalbazaar/forge/security/advisories/GHSA-q67f-28xg-22rw
GitHub commit

commit bdecf11571c9 (digitalbazaar/forge)

Fix landed in digitalbazaar/forge commit bdecf11571c9 — awaiting tagged release

https://github.com/digitalbazaar/forge/commit/bdecf11571c9f1a487cc0fe72fe78ff6dfa96b85
Web page

RFC 8032 - Edwards-Curve Digital Signature Algorithm (EdDSA)

https://datatracker.ietf.org/doc/html/rfc8032#section-8.4

Vendor Advisories for CVE-2026-33895(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcluster-observability-operator/logging-console-plugin-pf4-rhel9:17828392792026-07-01redhat
redhatautomation-gateway-0:2.5.20260422-3.el9ap2026-06-09redhat
redhatrhdh/rhdh-hub-rhel9:17779032622026-05-05redhat
redhatrhdh/rhdh-hub-rhel9:17767842862026-04-22redhat

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.0: fixed in 1.4.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 35× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 98 of 235 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 137 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-18 03:46 UTCEG score recompute
  8. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-17 15:41 UTCEG score recompute
  10. 2026-10-17 15:41 UTCVendor advisory
  11. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-14 19:24 UTCOSV refresh
  14. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  15. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  16. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-12 16:13 UTCEG score recompute
  18. 2026-10-11 19:55 UTCEG score recompute
  19. 2026-10-11 17:08 UTCEG score recompute
  20. 2026-10-11 14:35 UTCEG score recompute
  21. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Show 73 more
  1. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  2. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  3. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  4. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  5. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  6. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  7. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  8. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  9. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  11. 2026-09-23 19:04 UTCOSV refresh
  12. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  16. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  19. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  26. 2026-09-04 13:30 UTCEG score recompute
  27. 2026-09-04 13:30 UTCVendor advisory
  28. 2026-09-04 12:25 UTCEG score recompute
  29. 2026-09-04 12:25 UTCVendor advisory
  30. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  32. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  33. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  34. 2026-08-31 13:37 UTCEG score recompute
  35. 2026-08-31 13:37 UTCVendor advisory
  36. 2026-08-31 12:31 UTCEG score recompute
  37. 2026-08-31 12:31 UTCVendor advisory
  38. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  39. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  40. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  41. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  42. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  43. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  44. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  45. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  46. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  47. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  48. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  49. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  50. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  51. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  52. 2026-08-16 09:56 UTCEG score recompute
  53. 2026-08-16 09:56 UTCVendor advisory
  54. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  55. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  56. 2026-08-14 19:11 UTCVendor advisory
  57. 2026-08-14 06:15 UTCEG score recompute
  58. 2026-08-14 06:15 UTCVendor advisory
  59. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  60. 2026-08-12 20:34 UTCEG score recompute
  61. 2026-08-12 20:34 UTCVendor advisory
  62. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  63. 2026-08-11 20:43 UTCEG score recompute
  64. 2026-08-11 20:43 UTCVendor advisory
  65. 2026-08-11 03:44 UTCEG score recompute
  66. 2026-08-11 03:44 UTCVendor advisory
  67. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  68. 2026-08-10 06:24 UTCVendor advisory
  69. 2026-08-09 18:06 UTCEG score recompute
  70. 2026-08-09 18:06 UTCVendor advisory
  71. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  72. 2026-08-09 05:48 UTCEG score recompute
  73. 2026-08-09 05:48 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33895?
CVE-2026-33895 is a high-severity vulnerability; its CVE record was published on March 27, 2026. Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, Ed25519 signature verification accepts forged non-canonical signatures where the scalar S is not reduced modulo the group order (S >= L). A valid signature and its S + L…
When was the CVE record for CVE-2026-33895 published?
The CVE record for CVE-2026-33895 was published on March 27, 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 September 4, 2026; the record at its source may have been updated since.
Is CVE-2026-33895 actively exploited?
CVE-2026-33895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33895?
CVE-2026-33895 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-33895?
A fix for CVE-2026-33895 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-33895 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-33895

Explore →

Is Your Infrastructure Affected by CVE-2026-33895?

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

Book a Demo →Browse All CVEs