CyberSecBulletin

Digitalbazaar vulnerabilities

We track 15 vulnerabilities in Digitalbazaar products. 15 are rated high or critical, and none are known to be exploited. The most recent was published on November 10, 2026.

15vulnerabilities
1critical
14high
0exploited
7.6average CVSS score

Latest Digitalbazaar vulnerabilities

  • 7.4 High severity

    forge: Improper Certificate Validation

    CVE-2026-125336Digitalbazaar

    Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, pki.verifyCertificateChain() in lib/x509.js does not decode or enforce the X.509 nameConstraints extension while validating certificate paths.

  • 7.5 High severity

    forge: Uncontrolled Resource Consumption

    CVE-2026-119191Digitalbazaar

    Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used asn1.fromDer(), BIT STRING decoding, maxDepth to process the relevant input or security decision. node-forge d

  • 7.4 High severity

    forge: Improper Certificate Validation

    CVE-2026-119190Digitalbazaar

    Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge parsed deprecated extension OIDs 2.5.29.10 and 2.5.29.13 as basicConstraints, and pki.verifyCertificateChain() used the first extens

  • 7.5 High severity

    forge: Uncaught Exception

    CVE-2026-119188Digitalbazaar

    Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), fragmented handshake message, interleaved record to process the relevant input o

  • 7.5 High severity

    forge: Uncontrolled Recursion

    CVE-2026-119187Digitalbazaar

    Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), TLS record processing, process() to process the relevant input or security decis

  • 7.5 High severity

    forge: Improper Validation of Integrity Check Value

    CVE-2026-118782Digitalbazaar

    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 return

  • 7.5 High severity

    forge: Uncontrolled Resource Consumption

    CVE-2026-118779Digitalbazaar

    Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used pem.decode(), lib/pem.js, missing END line to process the relevant input or security decision. node-forge used

  • 7.5 High severity

    forge: Improper Verification of Cryptographic Signature

    CVE-2026-85393Digitalbazaar

    node-forge through 1.4.0 fails to validate element count in nested DigestAlgorithm sequences during RSA PKCS#1 v1.5 signature verification. Attackers can embed garbage bytes inside the DigestAlgorithm sequence to forge valid signatures for arbitrary messages u

  • 9.1 Critical severity

    forge: Improper Certificate Validation

    CVE-2026-33896Digitalbazaar

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, `pki.verifyCertificateChain()` does not enforce RFC 5280 basicConstraints requirements when an intermediate certificate lacks both th

  • 7.5 High severity

    forge: Improper Verification of Cryptographic Signature

    CVE-2026-33895Digitalbazaar

    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 >

  • 7.5 High severity

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in…

    CVE-2026-33894Digitalbazaar

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). Attackers can forge signature

  • 7.5 High severity

    forge: Loop with Unreachable Exit Condition

    CVE-2026-33891Digitalbazaar

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.4.0, a Denial of Service (DoS) vulnerability exists in the node-forge library due to an infinite loop in the BigInteger.modInverse() funct

  • 7.5 High severity

    forge: Uncontrolled Recursion

    CVE-2025-66031Digitalbazaar

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that

  • 7.5 High severity

    forge: Improper Verification of Cryptographic Signature

    CVE-2022-24772DigitalbazaarEPSS 1.11%

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code does not check for tailing garbage bytes after decoding a `DigestInfo` ASN.1 structure. T

  • 7.5 High severity

    forge: Improper Verification of Cryptographic Signature

    CVE-2022-24771Digitalbazaar

    Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure