forge: Improper Verification of Cryptographic Signature
CVE-2026-33895 is a high-severity improper verification of cryptographic signature vulnerability in forge from Digitalbazaar, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected forge versions: < 1.4.0. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.54% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of forge you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Digitalbazaar | forge | < 1.4.0 | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2.5 for RHEL 9 | Not specified in the record | Not stated |
| Red Hat | Cluster Observability Operator 1.5.0 | Not specified in the record | Not stated |
| Red Hat | Red Hat Developer Hub 1.8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Developer Hub 1.9 | Not specified in the record | Not stated |
| Red Hat | Cryostat 4 | Not specified in the record | Not stated |
| Red Hat | Logging Subsystem for Red Hat OpenShift | Not specified in the record | Not stated |
| Red Hat | Red Hat Ansible Automation Platform 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Apache Camel - HawtIO 4 | Not specified in the record | Not stated |
| Red Hat | Red Hat build of Apicurio Registry 2 | Not specified in the record | Not stated |
| Red Hat | Red Hat Build of Podman Desktop | Not specified in the record | Not stated |
| Red Hat | Red Hat Data Grid 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Fuse 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Process Automation 7 | Not specified in the record | Not stated |
| Red Hat | Red Hat Quay 3 | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by CNA (github.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (github.com) |
| CVSS 3.1 | 7.5 | High | CNA |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Verification of Cryptographic Signature
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
More Improper Verification of Cryptographic Signature vulnerabilities (CWE-347)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Third-party and government advisories
- datatracker.ietf.org/doc/html/rfc8032#section-8.4Third Party Advisory
Other references
- access.redhat.com/errata/RHSA-2026:13826
- access.redhat.com/errata/RHSA-2026:24761
- access.redhat.com/errata/RHSA-2026:34342
- access.redhat.com/errata/RHSA-2026:9742
- access.redhat.com/security/cve/CVE-2026-33895
- bugzilla.redhat.com/show_bug.cgi?id=2452457
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33895.json
Other vulnerabilities in forge
- 7.4 High severity
- 7.5 High severity
- 7.4 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Recent Improper Verification of Cryptographic Signature vulnerabilities
- 7.5 High severity
- 9.1 Critical severity
- 9.0 Critical severity
- 7.5 High severity
- 9.1 Critical severity
- 8.8 High severity
Spotted an error? Tell us.