Skip to content
Fencer Intel
low 3.7

CVE-2026-125335 json

Forge: Ed25519 signature verification accepts small-order public keys

published 8d ago modified yesterday also EUVD-2026-122797 , GHSA-6889-vf6x-f3g5

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 10%
public exploits
0
none known

Summary

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, ed25519.verify() decodes a public key in crypto_sign_open() without rejecting small-order points or their non-canonical encodings. With S = 0 and a small-order R value, an attacker who can choose the public key can produce signatures that verify for many messages, or all messages with the identity key, without a private key. This can defeat proof-of-possession, attribution, non-repudiation, or deduplication checks that rely on a signature being bound to the message. Keys produced by normal Ed25519 key generation are not small-order, so applications that verify only trusted or internally generated public keys are not affected. This issue is fixed in version 1.4.3.

Patch / fix

  • npm node-forge 1.4.3

Is CVE-2026-125335 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-125335 updated cvss 3.7

node-forge: node-forge: Signature verification bypass via unvalidated small-order Ed25519 public keys

  • Red Hat Node HealthCheck Operator workload-availability/node-remediation-console-rhel8, workload-availability/node-healthcheck-rhel9-operator, workload-availability/node-healthcheck-operator-bundle, workload-availability/node-healthcheck-must-gather-rhel9
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat OpenShift Pipelines openshift-pipelines/pipelines-hub-ui-rhel9 Red Hat OpenShift Serverless openshift-serverless-1/logic-rhel9-operator
    affected: workaround, no fix available “Fix deferred”
  • Red Hat OpenShift Service Mesh 3 openshift-service-mesh/kiali-rhel9-operator, openshift-service-mesh/kiali-operator-bundle
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat 3scale API Management Platform 2 3scale-amp2/system-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Ansible Automation Platform 2 ansible-automation-platform-24/lightspeed-rhel8, automation-eda-controller 1.0.10-0.1.20260317.git9cae940.el8ap Red Hat Ceph Storage 4 rhceph/rhceph-4-dashboard-rhel8
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Connectivity Link 1 rhcl-1/rhcl-rhdh-dynamic-plugin-rhel9 Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9, rhdh/red-hat-developer-hub-backstage-plugin-lightspeed-backend, rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend Red Hat Developer Hub 2 rhdh/rhdh-hub-rhel10, rhdh/backstage-community-plugin-tech-radar-backend, rhdh/backstage-plugin-catalog-backend-module-gitlab, rhdh/red-hat-developer-hub-backstage-plugin-quickstart, rhdh/backstage-plugin-catalog-backend-module-gitlab-org, rhdh/red-hat-developer-hub-backstage-plugin-global-header, +6 more Red Hat Enterprise Linux 8 pcs, pcs-snmp, pcs 0.12.0-3.el10_0.5 Red Hat Enterprise Linux 9 pcs, pcs-snmp, pcs 0.12.0-3.el10_0.5 Red Hat Enterprise Linux 10 pcs 0.12.0-3.el10_0.5
    +2 more products
    Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/bootc-gaudi-rhel9, rhelai3/disk-image-cuda-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-feature-server-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Quay 3 quay/quay-rhel8, quay/quay-rhel9
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Self-service automation portal 2 ansible-automation-platform/automation-portal, ansible-automation-platform/bootc-automation-portal-rhel9
    affected: workaround, no fix available “Fix deferred”
show 1 more
  • Red Hat AMQ Broker 7 amq-broker-bin.zip 7.14.2.CR1, amq-broker-maven-repository.zip 7.14.2.CR1 Red Hat Ansible Automation Platform 2 automation-controller 4.5.39-1.el9ap, automation-platform-ui 2.6.15-1.el9ap, automation-gateway 2.5.20260923-1.el9ap Red Hat build of Apache Camel for Spring Boot 4 rhaf-camel-spring-boot-maven-repository.zip 4.18.4.CS6, rhaf-camel-for-springboot-maven-repository.zip 3.5.16.CS2 Red Hat Build of Podman Desktop rh-podman-desktop 3c6fc75a2a6cf5bb9b8a667fddcbbf428132badc Red Hat Enterprise Linux 8 grafana, grafana-loki, grafana-mssql, grafana-mysql, grafana-selinux, grafana-graphite, +9 more Red Hat Enterprise Linux 9 grafana, grafana-selinux, grafana 12.4.3-2.el10
    +3 more products
    Red Hat Enterprise Linux 10 grafana 12.4.3-2.el10 Red Hat Fuse 7 redhat-fuse-sources.zip 7.13.0, redhat-fuse-maven-repository.zip 7.13.0 Red Hat Hardened Images grafana13.1 13.1.9-0.1.hum1, grafana13.2 13.2.4-0.7.hum1, grafana12.4 12.4.13-0.6.hum1
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm node-forge
<1.4.3
1.4.3

Affected products

  • digitalbazaar forge

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of digitalbazaar/forge published their own advisory on GitHub. Reviewed sources take precedence over it.