Skip to content

Bump node-forge from 1.4.0 to 1.4.2 in /sdks/typescript - #40918

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/sdks/typescript/node-forge-1.4.2
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/sdks/typescript/node-forge-1.4.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 30, 2026

Copy link
Copy Markdown
Contributor

Bumps node-forge from 1.4.0 to 1.4.2.

Changelog

Sourced from node-forge's changelog.

1.4.2 - 2026-10-27

Fixed

  • [pem] Convert non-string input to a string in pem.decode() as before 1.4.1. The 1.4.1 PEM ReDoS fix (GHSA-7wch-p9px-956x) caused a TypeError for Buffer input, which is used by node-jose. (#1165)

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

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

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.

Bumps [node-forge](https://github.com/digitalbazaar/forge) from 1.4.0 to 1.4.2.
- [Changelog](https://github.com/digitalbazaar/forge/blob/main/CHANGELOG.md)
- [Commits](digitalbazaar/forge@v1.4.0...v1.4.2)

---
updated-dependencies:
- dependency-name: node-forge
  dependency-version: 1.4.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Oct 30, 2026
@github-actions github-actions Bot added typescript size/s S: 10-49 lines changed labels Oct 30, 2026

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📋 Review Summary

This PR is an automated Dependabot update that bumps the transitive dev dependency node-forge from 1.4.0 to 1.4.2 in sdks/typescript/package-lock.json to address several high-severity security vulnerabilities (including CVE-2026-85393 and CVE-2026-119192) and a subsequent regression fix in 1.4.2. The lockfile update is clean and safe to merge.

🔍 General Feedback

  • The lockfile also syncs the root apache-beam package version from 2.78.0-SNAPSHOT to 2.79.0-SNAPSHOT to match sdks/typescript/package.json.
  • No issues found.

💡 Tip: Comment /gemini review on this pull request to trigger a new Gemini code review.

@github-actions

Copy link
Copy Markdown
Contributor

Assigning reviewers:

R: @tvalentyn added as fallback since no labels match configuration
Backup reviewer: jrmccluskey (if the main reviewer is unresponsive, you can escalate to them by tagging their username)

Note: If you would like to opt out of this review, comment assign to next reviewer.

Available commands:

  • stop reviewer notifications - opt out of the automated review tooling
  • remind me after tests pass - tag the comment author after tests pass
  • waiting on author - shift the attention set back to the author (any comment or push by the author will return the attention set to the reviewers)

The PR bot will only process comments in the main thread (not review comments).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code Next Action: Reviewers size/s S: 10-49 lines changed typescript

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants