chore(deps): security-focused lock refresh (framework pinned, runtime-verified)#15
Merged
Conversation
sidxz
changed the title
Full refresh now that the access-log fix (framework-robust _route_template) is on main, so starlette 1.x is safe. Clears every lockfile HIGH advisory: cryptography 46->49, pyjwt 2.11->2.13, python-multipart 0.0.22->0.0.32, urllib3 2.6->2.7, mako 1.3.10->1.3.12, and starlette 0.52->1.3 (the SSRF/cred-theft + form-limit CVEs). Plus redis 8, structlog 26, sqlalchemy 2.0.51, uvicorn 0.49, fastapi 0.138. Verified: trivy fs exit 0, service tests 230 pass, access-log resolves real route templates on starlette 1.3.1, redis-py 8 TLS ping OK, app boots clean. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sidxz
force-pushed
the
chore/uv-lock-upgrade
branch
from
4f5ea87 to
55dbdfb
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
1 participant
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.
Refreshes
uv.lockto clear dependency advisories, scoped to avoid a web-frameworkbreak found by booting the real service.
What happened
A blanket
uv lock --upgradepulledfastapi 0.137+starlette 1.x, whose routingrework stops setting
scope["endpoint"]. That makesAccessLogMiddlewareloghttp.route="__unmatched__"for every request — silently, because the unit testuses a small middleware stack that still propagates
scope["endpoint"]while the real8-middleware stack doesn't. Caught only by running the app (
TestClientcapture ofhttp.routeon the realsrc.main:app).Scope (this PR)
cryptography 49,pyjwt 2.13,python-multipart 0.0.32,urllib3 2.7,mako 1.3.12redis 8(TLS ping OK),structlog 26(log output byte-identical to 25),sqlalchemy 2.0.51,uvicorn 0.49,pydantic 2.13fastapi<0.136,starlette<1.0— neither is a security advisoryVerification (real app, not just CI)
/health,/.well-known/jwks.json,/auth/providersall 200; migrations run; 0 startup errors/auth/providers,/authz/resolve; 404 →__unmatched__)redis-py 8.0.0→ redis 7.4.8 over TLS: PING + SET/GET roundtrip OKDeferred (needs a real starlette 1.x migration)
2 starlette HIGH advisories are only fixed in 1.x and remain:
CVE-2026-48818(SSRF/NTLM via UNC paths) — Windows-specific, N/A on the Linux containerCVE-2026-54283(form-limit bypass) — mitigated byMaxBodySizeMiddlewareClearing these requires moving to starlette 1.x, which must also make
_route_templateversion-robust (re-match instead of relying on
scope["endpoint"]) + audit other 1.xbehavior changes. Tracked as follow-up.
🤖 Generated with Claude Code