Skip to content

fix(security): clear pyjwt, DRF, sqlparse, urllib3 and grpc AR CVEs - #162

Merged
thomasrockhu-codecov merged 1 commit into
masterfrom
th/slack-app-cve-nov
Nov 2, 2026
Merged

thomasrockhu-codecov merged 1 commit into
masterfrom
th/slack-app-cve-nov

Conversation

@thomasrockhu-codecov

Copy link
Copy Markdown
Contributor

Clears the remaining crit/high findings in the codecov-slack-app AR image.

package from to how
pyjwt 2.13.0 2.15.1 lock refresh
djangorestframework 3.17.1 3.18.3 lock refresh; needs Django 5.2
django 5.1.15 5.2.18 requirements.in range moved to the 5.2 LTS line
sqlparse 0.5.5 0.6.1 lock refresh
urllib3 2.7.0 2.8.0 lock refresh
google.golang.org/grpc (berglas) 1.82.1 1.84.0 berglas v2.0.15 → v2.0.18
github.com/go-jose/go-jose/v4 (berglas) 4.1.4 4.1.6 berglas v2.0.18
expat (apk) 2.9.0-r0 2.10.0-r0 requirements image rebuild (apk add --upgrade expat)

berglas v2.0.18 already pins grpc/x-crypto/x-net at or above our previous go get pins, so those pins are dropped and the build is a plain rebuild of the release tag on the Go 1.27.3 toolchain.

requirements.txt was regenerated with targeted pip-compile --upgrade-package in python:3.12-alpine3.21, so nothing else moved.

Testing

  • Ran the test suite against Postgres 14 with the old and new locks: identical results (80 pass; the same 14 env-dependent tests fail on master too).
  • makemigrations --check: no changes under Django 5.2.

Made with Cursor

…CVEs

DRF 3.18.2 requires Django 5.2, so move to the 5.2 LTS line (also clears
the django 5.1 high). berglas v2.0.18 already ships patched grpc/go-jose,
so the go get pins are no longer needed.

Co-authored-by: Cursor <cursoragent@cursor.com>
@thomasrockhu-codecov
thomasrockhu-codecov merged commit c1c85c6 into master Nov 2, 2026
4 checks passed
@thomasrockhu-codecov
thomasrockhu-codecov deleted the th/slack-app-cve-nov branch November 2, 2026 18:30

This branch was successfully deployed

1 active deployment
staging — c35e7048 Deployed Nov 2, 2026 by thomasrockhu-codecov via Build and Push #7
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.

2 participants