Skip to main content
Public proof of conceptFix available

CVE-2026-33895

A public proof of concept exists; no exploitation attested.

  • Published2026-03-27
  • Fixed in1.4.0
  • WeaknessCWE-347

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-03-2721:17CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-33895?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-33895?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

OSV · NVD
node-forge
BranchAffectedFixed in
1.4< 1.4.01.4.0
Digitalbazaar forge
BranchAffectedFixed in
1.3≤ 1.3.3no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • RHSA-2026:86618 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: New container image: rhceph-9.2

  • RHSA-2026:34342 Red Hat Product Security4 products fixed

    Red Hat Security Advisory: Cluster Observability Operator 1.5.0

  • RHSA-2026:24761 Red Hat Product Security2 products fixed

    Red Hat Security Advisory: Red Hat Ansible Automation Platform 2.5 Product Security and Bug Fix Update

  • RHSA-2026:13826 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat Developer Hub 1.9.4 release.

  • RHSA-2026:9742 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Red Hat Developer Hub 1.8.6 release.

Full record on NVD

Fix

  1. Update node-forge to 1.4.0
  2. Vendor fix Red Hat Product Security RHSA-2026:86618 · 4 productsThe container images provided by this update can be downloaded from the Red Hat container registry at registry.redhat.io using the "podman pull" command.
  3. Vendor fix Red Hat Product Security RHSA-2026:34342 · 4 productsBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  4. Vendor fix Red Hat Product Security RHSA-2026:24761 · 2 productsFor details on how to apply this update, refer to Ansible Automation Platform documentation.
  5. Vendor fix Red Hat Product Security RHSA-2026:13826 · 1 productFor more about Red Hat Developer Hub, see References links
  6. Workaround from the vendor Red Hat Product Security RHSA-2026:86618 · 28 productsMitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionpoc2026-03-31
  • OpenCVESSVC decisionpoc—
  • CNACVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-347read 2026-10-23
  • FIRST EPSSEPSS score0.5 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Published
2026-03-27
Last Modified
2026-09-04
NVD status
Modified

Frequently asked questions

What is CVE-2026-33895?

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.

Is CVE-2026-33895 actively exploited?

A proof-of-concept exploit exists for CVE-2026-33895, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2026-33895?

CVE-2026-33895 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N.

Running node-forge? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month