Skip to content

fix(deps): bump cryptography to 50.0.0 (CVE-2026-69247, HIGH) - #45

Closed
seonghobae wants to merge 1 commit into
mainfrom
sec/cryptography-50
Closed

seonghobae wants to merge 1 commit into
mainfrom
sec/cryptography-50

Conversation

@seonghobae

Copy link
Copy Markdown
Contributor

The org trivy-fs gate fails every open PR on this repo:

[HIGH (security-severity=8.0)] CVE-2026-69247 requirements.txt:125 - Package: cryptography

CVE-2026-69247: PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle through distinguishable errors and timing. Vulnerable: >=44.0.0 <50.0.0; patched: 50.0.0.

Bumps cryptography 49.0.0 → 50.0.0 with hash pins refreshed from PyPI (46 artifacts, sorted). The existing cffi==2.1.0 pin satisfies cryptography 50's new cffi>=2.0.0 requirement, so no other pins change.

Unblocks #42 and every other open PR on this repo (trivy-fs gate). Note: the Semgrep gate has separate pre-existing code findings (authz.py, graph_store.py) tracked separately.

🤖 Generated with Claude Code

PKCS#7 EnvelopedData decryption exposes a Bleichenbacher oracle
(HIGH, security-severity 8.0); patched in 50.0.0. Hash pins refreshed
from PyPI. cffi pin (2.1.0) already satisfies the new cffi>=2.0.0
requirement. Clears the trivy-fs gate blocking all open PRs.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 2 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: b08380b3-a467-4887-8180-abd2c427ba6e

📥 Commits

Reviewing files that changed from the base of the PR and between 9a7088e and 9a042d4.

📒 Files selected for processing (1)
  • requirements.txt

Comment @coderabbitai help to get the list of available commands.

Copy link
Copy Markdown
Contributor Author

Closing as superseded by #50. PR #50 contains the same cryptography 50.0.0 CVE remediation and consolidates the accompanying exact-head security gates, JWKS transport fix, regression coverage, authoritative lock regeneration, and 100% statement/branch coverage enforcement. Consolidation prevents parallel lockfile branches and stale-head validation.

@seonghobae seonghobae closed this Aug 5, 2026
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.

1 participant