GeezerVison

Sourced from node-forge's changelog.

1.4.1 - 2026-10-27

Notes

• This release involved coordinating many security reports from many groups, people, and robots over too long period of time. Thank you for your reports and patience.
• Claude Code was used to help organize, track, untangle, merge, test, validate, fix, and improve it all. Further verification of fixes would be welcome.
• Tracking credits was challenging for some issues due to multiple email and GitHub reports, incomplete contact details, or combining of partial reports and fixes. Please let us know if there are credits changes needed here or in advisory data.

Security

• HIGH: Signature forgery in RSA-PKCS due to ASN.1 extra field in DigestAlgorithm.
  • RSASSA PKCS#1 v1.5 signature verification accepts forged signatures for low public exponent keys (e=3). The fix for CVE-2026-33894 only checked the element count of the outer DigestInfo. Attackers can add "garbage" elements inside the nested DigestAlgorithm SEQUENCE in order to construct a signature that passes verification, enabling Bleichenbacher style forgery.
  • Reported by Geo (@​geo-chen).
  • CVE ID: CVE-2026-85393
  • GHSA ID: GHSA-2g46-22mc-6gwp
• HIGH: Signature forgery in RSA-PKCS due to non-canonical DigestInfo encoding.
  • RSASSA PKCS#1 v1.5 signature verification accepts non-canonical DigestInfo encodings, such as NULL parameters with content, non-minimal length encodings, and non-canonical OIDs. These provide attackers space to construct forged signatures for low public exponent keys (e=3), similar to CVE-2026-33894 and CVE-2026-85393.
  • Reported by Oren Yomtov (@​orenyomtov, Fireblocks), Bronson Yen (Calif.io, in collaboration with Claude and Anthropic Research), Kamil Hałajda, @​pzartech, @​antonlissone, and @​Brechard.
  • CVE ID: CVE-2026-119192
  • GHSA ID: GHSA-6qrw-m8cv-hcxf
• HIGH: ASN.1 resource exhaustion via BIT STRING decoding.
  • An Uncontrolled Recursion (CWE-674) and Uncontrolled Resource Consumption (CWE-400) vulnerability in node-forge versions 1.4.0 and below enables remote, unauthenticated attackers to exhaust CPU and memory with small crafted DER or PEM inputs (certificates, keys, and other structures parsed with asn1.fromDer()). By default fromDer() attempts to decode BIT STRING contents as ASN.1. That decode ignored the global asn1.maxDepth and the per-call maxDepth option, and BIT STRINGs nested in decoded BIT STRINGs were decoded too, with each level keeping a full copy of its decoded contents. Memory use grew quadratically with the nesting depth and can terminate the process from heap exhaustion. The maxDepth bypass is an incomplete fix of CVE-2025-66031.
  • Reported by:

... (truncated)

• 8a91737 Release 1.4.1.
• fdd1b9f Update changelog.
• 4c1c3e3 Add changelog release notes.
• 0b455eb Ignore TLS heartbeat requests before the handshake.
• e96c47b Fix jsbn modInverse hang with negative inputs.
• f655560 Fix x509 CA store modification in chain verification.
• 797c3f8 Prevent prototype pollution from cookies in forge.http.
• 81774ff Require valid PKCS#7 padding in CBC and ECB decryption.
• 236845d Add AES-GCM tag length checks.
• c7f4261 Verify certificate signatures with the child's scheme.
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.