fix(deps): update dependency @noble/curves to v2.4.0 - #6
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/noble-curves-2.x
branch
4 times, most recently
from
July 30, 2026 13:55
46864d9 to
55df78d
Compare
renovate
Bot
force-pushed
the
renovate/noble-curves-2.x
branch
from
August 6, 2026 10:51
55df78d to
4220ec7
Compare
renovate
Bot
force-pushed
the
renovate/noble-curves-2.x
branch
from
August 27, 2026 16:07
4220ec7 to
f2eab2a
Compare
renovate
Bot
force-pushed
the
renovate/noble-curves-2.x
branch
from
September 2, 2026 21:30
f2eab2a to
b1e8024
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.0.1→2.4.0Release Notes
paulmillr/noble-curves (@noble/curves)
v2.4.0Compare Source
0x00encoding.Special thanks to Red Team (Rob Hamilton, CalleBTC, Omer Talip) and 1Password's Off-by-1 Labs.
v2.3.0Compare Source
Security & constant-timeness
X25519 hardening
It was possible to execute a remote timing attack on X25519, across many samples, and learn up to 4.036 bits of long-term private key. Other 247 bits were NOT affected.
The impact: mainly fingerprinting (recognition of key across deployments), NOT key recovery, NOT X25519 breakage. Maintainer was also not able to escalate to co-residency (SMT).
Reported and found by:
geostergiop@aueb.gr)kpatsak@unipi.gr)Performance
ed25519, p256, p384, p521secp256k1.Point.BASE.precompute(8)(likewise for other curves).Misc
Full Changelog: paulmillr/noble-curves@2.2.0...2.3.0
v2.2.0Compare Source
Ed25519ZIP 215 verification to match the specification more strictly where its vectors were insufficient.Object.freezeto most primitives.Uint8Array, while TypeScript 5.9+ made it generic:Uint8Array<ArrayBuffer>.TS2345.Version 2.1 was skipped to align with other noble packages.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.