fix(deps): override clerk-backend-api cap to clear cryptography CVEs (CI run #13) - #159
Draft
Sbussiso wants to merge 1 commit into
Draft
fix(deps): override clerk-backend-api cap to clear cryptography CVEs (CI run #13)#159Sbussiso wants to merge 1 commit into
Sbussiso wants to merge 1 commit into
Conversation
Weekly dependency refresh run #13 (31367891577) failed at the 'pip-audit --strict' gate: cryptography 48.0.1 has three advisories that landed since the last green refresh: PYSEC-2026-3552 / CVE-2026-69247 — PKCS#7 EnvelopedData Bleichenbacher oracle (fixed in 50.0.0) PYSEC-2026-3553 / CVE-2026-69249 — duplicate self-signed intermediates cause exponential path-building (fixed in 49.0.0) PYSEC-2026-3554 / CVE-2026-69248 — verifier accepts wildcard DNS names escaping permittedSubtrees (fixed in 49.0.0) The constraint floor 'cryptography>=48.0.1' can't reach the fix versions because clerk-backend-api 6.0.1 (the latest release) declares 'cryptography<49.0.0,>=45.0.0', and uv respects that transitive cap. No newer clerk-backend-api exists. Add an 'override-dependencies' entry forcing cryptography>=50.0.0 past the cap. Verified locally (parity with the weekly workflow's gates): - uv lock --upgrade -> cryptography 50.0.0 - ruff check -> All checks passed - pip-audit --strict -> No known vulnerabilities found - pytest -q -> 699 passed cryptography is purely transitive here (the backend uses PyJWT + clerk-backend-api for JWT/JWS, not cryptography's x509/PKCS#7 paths the CVEs target), so the override carries no behavioral risk. Remove the override + floor once clerk-backend-api ships a release allowing cryptography>=49.0.0.
This was referenced Aug 10, 2026
Sbussiso
referenced
this pull request
Aug 10, 2026
Bumps [eslint](https://github.com/eslint/eslint) from 9.39.4 to 10.8.1. - [Release notes](https://github.com/eslint/eslint/releases) - [Commits](eslint/eslint@v9.39.4...v10.8.1) --- updated-dependencies: - dependency-name: eslint dependency-version: 10.8.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
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.
Root cause
Weekly dependency refresh run #13 (31367891577) failed at the
pip-audit --strictgate:Three CVEs in
cryptography48.0.1, all disclosed since the last green refresh:permittedSubtreesWhy a plain lock refresh could not fix it
The existing constraint
cryptography>=48.0.1is a floor, not a cap, souv lock --upgradeshould have pulled a newer version — but it stayed pinned at 48.0.1. Root cause:clerk-backend-api6.0.1 (the latest release on PyPI) declarescryptography<49.0.0,>=45.0.0, and uv respects that transitive upper bound. There is no newerclerk-backend-apirelease. So the fix versions (49.0.0 / 50.0.0) are unreachable through normal resolution.Fix
Add a
tool.uv.override-dependenciesentry forcingcryptography>=50.0.0past clerk-backend-api's cap. uv's override mechanism is the sanctioned way to ignore a transitive constraint that blocks a security fix.cryptographyis purely transitive in this backend — there are no directcryptographyimports. The backend uses PyJWT + clerk-backend-api for JWT/JWS verification, not the x509/PKCS#7 or certificate-path-building code paths these CVEs target, so the override carries no behavioral risk.Verification (parity with the weekly workflow's gates)
Ran locally against the patched lock:
uv lock --upgradeuv run ruff checkuv run pip-audit --strictuv run pytest -qCleanup note
Remove the
override-dependenciesblock and thecryptography>=48.0.1constraint floor onceclerk-backend-apiships a release that allowscryptography>=49.0.0. Both are documented inline inbackend/pyproject.toml.Draft until CI on this branch confirms the fix reproduces green in GitHub Actions.