Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-33894

node-forge: Forge: Signature Forgery via Weak RSASSA PKCS#1 v1.5 Verification

Overview

Published
27 Mar 2026
Modified
26 Oct 2026
High CVE
3 Registry packages
39 OS packages
4 Linux distributions
Yes Fix available

Description

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.

Source: OX vulnerability database

Severity

7.5 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Weakness: CWE-20, CWE-347

Affected packages · 3

Packages affected by CVE-2026-33894
EcosystemPackageVulnerableFixed in
npm node-forge <1.4.0 1.4.0
Seal npm @seal-security/node-forge >=0.10.0-sp1-for-passport-saml, <0.10.0-sp3p3>=1.3.1-sp1, <1.3.1-sp2 0.10.0-sp3p31.3.1-sp2
Seal npm node-forge >=0.10.0-sp0, <0.10.0-sp3p3>=1.3.1-sp0, <1.3.1-sp2 0.10.0-sp3p31.3.1-sp2

Open a package to see all its vulnerabilities.

Operating systems · 42 fixes

Red Hat 1 release · 1 package

affected 1
pcs
Red Hat fixes for CVE-2026-33894
ReleasePackageFixed in
9 pcs +1 affected

chainguard 1 release · 30 packages

fixed 30
kubeflow-katib kubeflow-centraldashboard gitlab-rails-ce-18-1 gitlab-rails-ce-fips-18-1 gitlab-rails-ce-18-10 gitlab-rails-ce-fips-18-10 +24
chainguard fixes for CVE-2026-33894
ReleasePackageFixed in
kubeflow-katib 0.19.0-r40
kubeflow-centraldashboard 1.10.0-r18
gitlab-rails-ce-18-1 18.1.6-r25
gitlab-rails-ce-fips-18-1 18.1.6-r87
gitlab-rails-ce-18-10 18.10.8-r12
gitlab-rails-ce-fips-18-10 18.10.8-r8

24 more rows

minimos 1 release · 7 packages

fixed 7
kubeflow-pipelines-frontend opensearch-dashboards-2 argo-workflows-3-6 argo-workflows-3-7 verdaccio kibana-8-19 +1
minimos fixes for CVE-2026-33894
ReleasePackageFixed in
kubeflow-pipelines-frontend 2.17.0-r0
opensearch-dashboards-2 +1 2.19.6-r0
argo-workflows-3-6 +1 3.6.17-r0
argo-workflows-3-7 +1 3.7.8-r0
verdaccio 6.3.0-r0
kibana-8-19 8.19.15-r0

1 more row

wolfi 1 release · 4 packages

fixed 4
kubeflow-katib kubeflow-centraldashboard kubeflow-pipelines opensearch-dashboards-3
wolfi fixes for CVE-2026-33894
ReleasePackageFixed in
kubeflow-katib 0.19.0-r40
kubeflow-centraldashboard 1.10.0-r18
kubeflow-pipelines 2.16.0-r11
opensearch-dashboards-3 3.5.0-r11

References

Show all 22 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.