fix(security): upgrade cryptography to 50.0.0 - #1232
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (9)
📝 WalkthroughWalkthroughThe PR updates Python and frontend security dependency pins, regenerates affected hashes and lockfiles, expands release-governance checks, and records the changes in the security changelog. ChangesDependency synchronization
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
PR governance metadata gate update for PR governance metadata gate is waiting on current-head requirements; see the latest check for pending reasons. |
|
@coderabbitai review Please review the exact current head |
|
✅ Action performedReview finished.
|
Summary
Remediate
CVE-2026-69247/GHSA-g6cj-pr64-35w5, a high-severity Bleichenbacher-oracle issue affectingcryptography >=44.0.0,<50.0.0, and synchronize the exact frontend lock with current scanner fixes discovered while validating the same head.This exact branch now commits the remediation directly:
cryptography==50.0.0;protobuf==6.33.6constraint becausegoogle-cloud-aiplatform==1.160.0requires protobuf<7while the backend remains onprotobuf==7.35.1;8.5.18to8.5.24forCVE-2026-69153;brace-expansionfrom5.0.8to5.0.9forGHSA-rgw5-rvv9-x895, andjsdom/undicito30.0.1/8.9.0for the newly disclosed Undici advisories;Security boundary
No vulnerability suppression, Trivy exception, release-age bypass, gate weakening, or source-data mutation is introduced. Runtime Fernet encryption/decryption and key-rotation behavior remains covered by the existing test suite.
Local verification at
dbfa8a94160d500830be39309bb31e853ea7b951cryptography==49.0.0; the frontend contracts failed against the stale PostCSS, jsdom, Undici, and brace-expansion lock state before their fixes.uv lock --check: pass.cryptography.__version__ == "50.0.0".1685 passed, 33 skipped.37 passed.23 passed.uv pip install --dry-run --require-hashes: pass, resolving105and102packages.49test files /427tests pass; ESLint, TypeScript, frozen pnpm install, and Next.js production build pass.pnpm audit --audit-level=moderate: zero advisories after the fix; before the fix it reported four Moderate and two High advisories.db3078af7c624355457601716f28be2df2f294c7(parentsc8ef4164...anddbfa8a94...): current Trivy vulnerability, secret, and misconfiguration scan at Medium/High/Critical returned zero findings.git diff --check: pass.The exact current head has passed Application CI, Dependency Review, Bandit, Semgrep, Docker-image validation, and the repository Security Scan. The PR is ready for independent review and protected auto-merge.