CVE-2026-33895

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 56% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: Elevated riskExposed: 0

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.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

March 27, 2026

Last Modified

September 4, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

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
generic

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

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

Vendor Advisories for CVE-2026-33895(5)

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 / EcosystemFixed in / 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 rangeFixed inDependents
node-forge—1.4.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 56× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 186 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33895?
CVE-2026-33895 is a high vulnerability 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 CVE-2026-33895 disclosed?
CVE-2026-33895 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on September 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33895 actively exploited?
CVE-2026-33895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 56.4% of all scored CVEs.
What is the CVSS score of CVE-2026-33895?
CVE-2026-33895 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33895?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33895, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs