cve.bz

CVE-2026-119186 digitalbazaar forge

5.9 mediumExploit referenceEPSS 0.2%Fix available

Medium (5.9) in digitalbazaar forge. EPSS 0.2% 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 did not validate the AES-GCM tagLength option passed to start() during decryption through forge.cipher.createDecipher(). When an application derived tagLength from received data or used an unset or zero-like configuration value, a value that converted to zero together with an empty or missing authentication tag caused the calculated and supplied tags to compare as empty, so decipher.finish() accepted unauthenticated ciphertext. Applications that omit tagLength to use the 128-bit default or pass a fixed valid tag length are unaffected. This issue is fixed in version 1.4.1.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 10th 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: no · Technical impact: partial, assessed 2026-10-29. 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-119186 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-119186?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-119186?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-119186 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-5cwg-6vw7-rj6pnpmnode-forge<1.4.11.4.1

Linux distributions

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

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 Moderate.

Red Hat's statement

Moderate severity is assigned to this flaw because successful exploitation requires specific non-default conditions where consumer applications dynamically derive encryption parameters or accept zero-length tags from untrusted input. Typical deployments across Red Hat environments utilize standard configurations that default to the 128-bit authentication tag, which prevents forged ciphertexts from being accepted. Consequently, the practical risk is constrained to implementations that explicitly expose tag length assignment to unvalidated external data.

ProductPackageStateAdvisory
Node HealthCheck Operatorworkload-availability/node-healthcheck-must-gather-rhel9Out of support scope
Node HealthCheck Operatorworkload-availability/node-healthcheck-operator-bundleOut of support scope
Node HealthCheck Operatorworkload-availability/node-healthcheck-rhel9-operatorOut of support scope
Node HealthCheck Operatorworkload-availability/node-remediation-console-rhel8Out of support scope
OpenShift Pipelinesopenshift-pipelines/pipelines-hub-ui-rhel8Fix deferred
OpenShift Pipelinesopenshift-pipelines/pipelines-hub-ui-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/logic-rhel9-operatorFix deferred
OpenShift Service Mesh 3openshift-service-mesh/kiali-operator-bundleOut of support scope
OpenShift Service Mesh 3openshift-service-mesh/kiali-rhel9-operatorOut of support scope
Red Hat AMQ Broker 7amq-broker-bin.zipFix deferred
Red Hat AMQ Broker 7amq-broker-maven-repository.zipFix deferred
Red Hat Ansible Automation Platform 2ansible-automation-platform-24/lightspeed-rhel8Out of support scope
Red Hat Ansible Automation Platform 2automation-controllerOut of support scope
Red Hat Ansible Automation Platform 2automation-eda-controllerOut of support scope
Red Hat Ansible Automation Platform 2automation-gatewayOut of support scope
Red Hat Ansible Automation Platform 2automation-platform-uiFix deferred
Red Hat build of Apache Camel for Spring Boot 4rhaf-camel-for-springboot-maven-repository.zipFix deferred
Red Hat build of Apache Camel for Spring Boot 4rhaf-camel-spring-boot-maven-repository.zipFix deferred
Red Hat Build of Podman Desktoprh-podman-desktopFix deferred
Red Hat Ceph Storage 4rhceph/rhceph-4-dashboard-rhel8Out of support scope
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-119186.

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