Skip to content

Security: fix scanner findings 2026-11-02 - #315

Draft
ChiefGyk3D wants to merge 1 commit into
mainfrom
claude/security-scan-2026-11-02
Draft

ChiefGyk3D wants to merge 1 commit into
mainfrom
claude/security-scan-2026-11-02

Conversation

@ChiefGyk3D

Copy link
Copy Markdown
Owner

Summary

Weekly security-scan triage.

Alert Tool Severity Change
code-scanning:5273 Snyk Open Source high dnspython pinned >=2.9.0,<3 directly in requirements.in (was resolving to 2.8.0 transitively via hypeman-social → atproto), fixing GHSA-45c3-73f7-pv4m

Fixes #314

Not in this PR

Test plan

  • uv pip compile requirements.in --universal --generate-hashes --python-version 3.11 -o requirements.txt — resolves dnspython==2.9.0 cleanly, no conflicts (atproto allows dnspython<3,>=2.4.0)
  • ruff check stream_daemon/ stream-daemon.py — all checks pass (unaffected by this change; requirements.in/.txt only)

Generated by Claude Code

dnspython comes in transitively via hypeman-social -> atproto (atproto
allows dnspython<3,>=2.4.0, no upper-bound conflict) and was resolving to
2.8.0. GHSA-45c3-73f7-pv4m: a crafted DNS message with a long compression
pointer chain causes excessive CPU use in dns.name.from_wire_parser().
Pinned explicitly rather than left to transitive resolution, per this
file's stated policy for security-relevant packages.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExYLARHpML7a27M29ZMM6q
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.

[Security] high Snyk: dnspython 2.8.0 excessive CPU use (CVE-2026-114605) — fixed in PR

2 participants