You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(deps): patch security advisories in rust and npm deps - #2413
dompurify 3.4.12 → 3.4.17, pulled in through mermaid (CVE-2026-116802, -116803, -116804).
Not fixed:crypto-bigint 0.5.5 (RUSTSEC-2026-0387). elliptic-curve 0.13 pins it, through k256 0.13, ecdsa 0.16, alloy-signer and openvm-ecc-guest. Clearing it needs the elliptic-curve 0.14 migration upstream. Guest lockfiles are untouched.
cargo check in templates/default and crates/openvm-prover: pass. openvm-prover was checked with SDKROOT set to the macOS 26.5 SDK, to get around a local Xcode SDK problem.
pnpm -F @interfold/mcp build and tsc --noEmit: pass.
docs: pnpm build passes on Next 15.5.28.
Under next start, /, /learn, /learn/what-is-e3 and /whitepaper return 200.
Old URLs redirect to their new pages: /introduction → /learn, /ciphernode-operators/running → /operate/running.
KaTeX renders on /learn/cryptography.
An osv-scanner re-scan finds none of the advisories above, apart from crypto-bigint 0.5.5.
Compatibility
Protocol review: no protocol effect.
The crypto-bigint 0.7 and ctutils dependencies come only through Noir's acvm_blackbox_solver ECDSA opcodes. No circuit uses them, so witnesses, proofs and VKs are unchanged.
The bundled libzstd is still 1.5.7, with byte-identical sources. zstd is used only for HTTP compression and OpenVM's internal STARK decoding.
libp2p-tls uses its own certificate verifier, so the peer wire format is unchanged.
Guest programs, image IDs, protocol-release.toml and vk-commitments.json are untouched.
Release follow-up: the root Cargo.lock feeds the circuit SOURCE_HASH (crates/zk/build/src/identity.rs), so this bump changes the hash for every circuit pair. The circuit artifacts themselves don't change. Before the next release, rebuild the circuits and push them to circuit-artifacts for the new hash, or download-circuits in releases.yml won't find a match.
Summary by CodeRabbit
Chores
Updated the tooling used to support browser-based testing, documentation-site builds, and image processing. These maintenance changes keep development and publishing workflows current; they do not change the features or behavior available in the product. No new user-facing functionality is included in this update.
Reviewing files that changed from the base of the PR and between 4f8271e and cb5fe03.
Files ignored due to path filters: 4
Cargo.lock is excluded by !**/*.lock
crates/openvm-prover/Cargo.lock is excluded by !**/*.lock
pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
templates/default/Cargo.lock is excluded by !**/*.lock
Files selected for processing: 3
crates/wasm/package.json
docs/package.json
packages/interfold-mcp/package.json
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
Walkthrough
Three package manifests update dependency versions: Playwright for WASM, Next.js and Sharp for the documentation site, and the Model Context Protocol SDK for the MCP package.
Playwright changes from 1.52.0 to 1.64.1. Next.js changes from ^14.2.1 to ^15.5.28, and Sharp changes from ^0.34.1 to ^0.35.5. The Model Context Protocol SDK changes from ^1.10.2 to ^1.32.2.
The dependency updates present no established merge-blocking issue in the supplied evidence. Merge after normal checks, retaining the documented circuit rebuild and publication step before the next release.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly and concisely describes the main change: patching security advisories in Rust and npm dependencies.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (3 skipped: 3 unsupported.)
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Some tools did not complete. Review the errors below.
ESLint
If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.
crates/wasm/package.json
ESLint skipped: missing config or dependency (missing-dependency). The ESLint configuration references a package that is not available in the sandbox.
docs/package.json
ESLint skipped: the matched ESLint configuration already failed (missing-dependency).
packages/interfold-mcp/package.json
ESLint skipped: the matched ESLint configuration already failed (missing-dependency).
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
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
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.
What and why
This PR bumps dependencies that have security advisories published between August and November 2026. osv-scanner found them in this repo.
Rust lockfiles (
Cargo.lock,crates/openvm-prover/Cargo.lock,templates/default/Cargo.lock)rustls-webpkiwebpki-roots,webpki-root-certsrustlszstd/zstd-safe/zstd-syscrypto-bigint0.7 /ctutilsnpm (
pnpm-lock.yaml)docs:next^14.2.1 → ^15.5.28. Next 14.x has no fix for the unauthenticated Image Optimization RCEs (GHSA-2xp9-vwfh-vxw4, GHSA-2464-fhr4-w9xw), CVE-2026-75604 or CVE-2026-94482. Nextra 2 and the pages router run unchanged on 15.5.sharp^0.34.1 → ^0.35.5 (CVE-2026-114111, CVE-2026-114112).packages/interfold-mcp:@modelcontextprotocol/sdk^1.10.2 → ^1.32.2 (CVE-2026-111767).crates/wasm:playwright1.52.0 → 1.64.1 (CVE-2025-59288, Chromium 136 → 156).dompurify3.4.12 → 3.4.17, pulled in throughmermaid(CVE-2026-116802, -116803, -116804).Not fixed:
crypto-bigint0.5.5 (RUSTSEC-2026-0387).elliptic-curve0.13 pins it, throughk2560.13,ecdsa0.16,alloy-signerandopenvm-ecc-guest. Clearing it needs theelliptic-curve0.14 migration upstream. Guest lockfiles are untouched.Verification
E3_ZK_PROVER_SKIP_FIXTURE_BUILD=1 cargo check --workspace --locked: pass.cargo checkintemplates/defaultandcrates/openvm-prover: pass.openvm-proverwas checked withSDKROOTset to the macOS 26.5 SDK, to get around a local Xcode SDK problem.pnpm -F @interfold/mcp buildandtsc --noEmit: pass.docs:pnpm buildpasses on Next 15.5.28.next start,/,/learn,/learn/what-is-e3and/whitepaperreturn 200./introduction→/learn,/ciphernode-operators/running→/operate/running./learn/cryptography.crypto-bigint0.5.5.Compatibility
Protocol review: no protocol effect.
crypto-bigint0.7 andctutilsdependencies come only through Noir'sacvm_blackbox_solverECDSA opcodes. No circuit uses them, so witnesses, proofs and VKs are unchanged.libp2p-tlsuses its own certificate verifier, so the peer wire format is unchanged.protocol-release.tomlandvk-commitments.jsonare untouched.Release follow-up: the root
Cargo.lockfeeds the circuitSOURCE_HASH(crates/zk/build/src/identity.rs), so this bump changes the hash for every circuit pair. The circuit artifacts themselves don't change. Before the next release, rebuild the circuits and push them tocircuit-artifactsfor the new hash, ordownload-circuitsinreleases.ymlwon't find a match.Summary by CodeRabbit