Skip to content

deps: pin python-dotenv >=1.2.2 (CVE-2026-28684) #51

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bk86a merged 2 commits into from
Apr 23, 2026
Merged

deps: pin python-dotenv >=1.2.2 (CVE-2026-28684) #51

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
aa81eed
deps: pin python-dotenv >=1.2.2 to fix CVE-2026-28684
bk86a Apr 23, 2026
84b0e1d
deps: bump python-dotenv to 1.2.2 in lockfile
bk86a Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion requirements.lock
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ idna==3.11
limits==5.8.0
pydantic==2.12.5
pydantic-settings==2.13.0
python-dotenv==1.0.1
python-dotenv==1.2.2
PyYAML==6.0.1
slowapi==0.1.9
starlette==0.52.1
Expand Down
1 change: 1 addition & 0 deletions requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,3 +4,4 @@ httpx>=0.27,<1
pydantic>=2,<3
pydantic-settings>=2,<3
slowapi>=0.1,<1
python-dotenv>=1.2.2,<2
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot Apr 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Regenerate lockfile after raising python-dotenv floor

This pin in requirements.txt does not actually change what gets audited or deployed, because both the security workflow (pip-audit -r requirements.lock in .github/workflows/ci.yml) and the container build (pip install -r requirements.lock in Dockerfile) consume requirements.lock, which still contains python-dotenv==1.0.1. As a result, the CVE fix is ineffective in production and the security job can remain blocked until the lockfile is updated to include a safe version.

Useful? React with 👍 / 👎.

Loading