cve.bz

CVE-2026-118782 digitalbazaar forge

7.5 highExploit referenceEPSS 0.1%Fix available

High (7.5) in digitalbazaar forge. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in node-forge 1.4.1.

On this page
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge accepted a PKCS#12 MAC or PKCS#12 password-based encryption iteration count of zero or less. pki.pbe.generatePkcs12Key() then returned a constant key independent of the password and salt, allowing crafted PKCS#12 input processed by forge.pkcs12.pkcs12FromAsn1() to bypass password-based integrity checks. Predictable encryption keys and IVs also affected PKCS#12 PBE using pbeWithSHAAnd3-KeyTripleDES-CBC or pbewithSHAAnd40BitRC2-CBC, including shrouded key bags, encrypted SafeContents, and PKCS#8 ENCRYPTED PRIVATE KEY input processed independently by forge.pki.decryptPrivateKeyInfo(). PBES2/PBKDF2-encrypted content is unaffected. This issue is fixed in version 1.4.1.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.1% (unchanged from 0.1% a week ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-11-03. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-354 Improper Validation of Integrity Check Value
CWE-1284 Improper Validation of Specified Quantity in Input
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-118782 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118782?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118782?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118782 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
digitalbazaar:forgebefore 1.4.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jc66-7q78-782gnpmnode-forge<1.4.11.4.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu20.04:LTS, 22.04:LTSnode-node-forgeno fix listedUBUNTU-CVE-2026-118782
Azure Linux3python-tensorboardno fix listedAZL-112501

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity flaw because it allows an attacker to bypass cryptographic integrity verifications without knowledge of the passphrase, enabling crafted credentials to appear trusted. Across Red Hat environments incorporating node-forge, impact depends on whether an application or management console accepts and processes user-supplied PKCS#12 or encrypted private key data. Systems that do not accept external certificate archives or that restrict administrative import mechanisms to authenticated users face minimal practical risk.

ProductPackageStateAdvisory
Node HealthCheck Operatorworkload-availability/node-healthcheck-must-gather-rhel9Affected
Node HealthCheck Operatorworkload-availability/node-healthcheck-operator-bundleAffected
Node HealthCheck Operatorworkload-availability/node-healthcheck-rhel9-operatorAffected
Node HealthCheck Operatorworkload-availability/node-remediation-console-rhel8Affected
OpenShift Pipelinesopenshift-pipelines/pipelines-hub-ui-rhel8Not affected
OpenShift Pipelinesopenshift-pipelines/pipelines-hub-ui-rhel9Affected
OpenShift Serverlessopenshift-serverless-1/logic-rhel9-operatorAffected
OpenShift Service Mesh 3openshift-service-mesh/kiali-operator-bundleNot affected
OpenShift Service Mesh 3openshift-service-mesh/kiali-rhel9-operatorNot affected
Red Hat AMQ Broker 7amq-broker-bin.zipNot affected
Red Hat AMQ Broker 7amq-broker-maven-repository.zipAffected
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Fix deferred
Red Hat Ansible Automation Platform 2automation-controllerFix deferred
Red Hat Ansible Automation Platform 2automation-eda-controllerFix deferred
Red Hat Ansible Automation Platform 2automation-gatewayFix deferred
Red Hat Ansible Automation Platform 2automation-platform-uiAffected
Red Hat build of Apache Camel for Spring Boot 4rhaf-camel-for-springboot-maven-repository.zipNot affected
Red Hat build of Apache Camel for Spring Boot 4rhaf-camel-spring-boot-maven-repository.zipNot affected
Red Hat Build of Podman Desktoprh-podman-desktopAffected
Red Hat Ceph Storage 4rhceph/rhceph-4-dashboard-rhel8Fix deferred
24 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-118782.

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-145 Checksum Spoofing Severity: Medium
  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

History

  1. Analyzed by the NVD

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON