Skip to content

[Snyk] Upgrade openpgp from 6.1.1 to 6.2.0 #21

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

bryronho
Copy link

snyk-top-banner

Snyk has created this PR to upgrade openpgp from 6.1.1 to 6.2.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released a month ago.

Release notes
Package name: openpgp
  • 6.2.0 - 2025-07-17

    What's Changed

    • Implement OpenPGP message grammar validation (add config.enforceGrammar, enabled by default) (#1853)
    • Enable using WebCrypto for X25519 when available (#1829)
    • Prefer subkeys with higher algorithm IDs (in case of equal creation timestamps), on the assumption that that's the most
      modern/secure algorithm (#1854)
    • Improve packet stream & error handling (#1856):
      • Packet parsing errors in not-yet-authenticated streams (i.e. SEIPDv1 with allowUnauthenticatedStream: true) get delayed until the decrypted data stream is authenticated
      • Non-critical unknown packets get turned into UnparseablePacket` objects on the packet stream instead of being ignored
    • Make Issuer Key ID signature subpacket non-critical (#1828)
    • Improve type definition for the User class (#1857)

    New Contributors

    Full Changelog: v6.1.0...v6.2.0

  • 6.1.1 - 2025-05-19
    • Address CVE-2025-47934 (Message signature verification could be spoofed)
from openpgp GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants