CVE-2026-33894

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 61% 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
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%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, RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signatures by stuffing “garbage” bytes within the ASN structure in order to construct a signature that passes verification, enabling Bleichenbacher style forgery. This issue is similar to CVE-2022-24771, but adds bytes in an addition field within the ASN structure, rather than outside of it. Additionally, forge does not validate that signatures include a minimum of 8 bytes of padding as defined by the specification, providing attackers additional space to construct Bleichenbacher forgeries. 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
0%
EPSS %ILE
40%
KEV
Not listed

Published

March 27, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Signature forgery in RSA-PKCS due to ASN.1 extra field · Advisory · digitalbazaar/forge · GitHub

https://github.com/digitalbazaar/forge/security/advisories/GHSA-ppp5-5v6c-4jwp
generic

RFC 2313 - PKCS #1: RSA Encryption Version 1.5

https://datatracker.ietf.org/doc/html/rfc2313#section-8

Vendor Advisories for CVE-2026-33894(11)

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

Patch Availability(11)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcluster-observability-operator/logging-console-plugin-pf4-rhel9:17828392792026-07-01redhat
redhatquay/quay-rhel8:17808913952026-06-09redhat
redhatautomation-gateway-0:2.5.20260422-3.el9ap2026-06-09redhat
redhatquay/quay-rhel8:17798114732026-06-04redhat
redhatquay/quay-rhel8:17798222612026-06-03redhat
redhatquay/quay-rhel8:17798114122026-06-02redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
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(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 41× 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 214 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-33894?
CVE-2026-33894 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, RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signatures by stuffing “garbage” bytes within the…
When was CVE-2026-33894 disclosed?
CVE-2026-33894 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33894 actively exploited?
CVE-2026-33894 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.0% of all scored CVEs.
What is the CVSS score of CVE-2026-33894?
CVE-2026-33894 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33894?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33894, 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-33894

Explore →

Is Your Infrastructure Affected by CVE-2026-33894?

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

Start Free Scan →Browse All CVEs