Skip to content

chore(deps): pin idna>=3.15 to clear CVE-2026-45409 #87

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 1 commit into from
May 22, 2026
Merged

chore(deps): pin idna>=3.15 to clear CVE-2026-45409 #87

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 @@ -11,7 +11,7 @@ h11==0.16.0
httpcore==1.0.9
httptools==0.7.1
httpx==0.28.1
idna==3.11
idna==3.16
limits==5.8.0
pydantic==2.12.5
pydantic-settings==2.13.0
Expand Down
2 changes: 2 additions & 0 deletions requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,3 +6,5 @@ pydantic-settings>=2.14.0,<3
slowapi>=0.1.9,<1
limits[redis]>=5.8.0
python-dotenv>=1.2.2,<2
# Transitive (via httpx); pinned to clear CVE-2026-45409
idna>=3.15,<4
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot May 22, 2026

Choose a reason for hiding this comment

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

P1 Badge Regenerate requirements.lock after pinning idna

The new idna>=3.15,<4 constraint in requirements.txt is not applied to the pinned lockfile, so CI’s dependency audit still reads idna==3.11 (.github/workflows/ci.yml runs pip-audit -r requirements.lock) and the Docker image still installs the vulnerable version from requirements.lock. In other words, this change doesn’t actually remediate the CVE in the audited/production dependency set until requirements.lock is regenerated and committed.

Useful? React with 👍 / 👎.

Loading