Repository navigation
[GHSA-jj36-9pvh-vj5r] Twisted: DNS Response Spoofing in twisted.names Due to Missing Source Address Validation - #10847
Conversation
|
Hi there @adiroiban! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository. This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory |
There was a problem hiding this comment.
🟢 Approval recommended
The narrowly scoped advisory update adds the official Twisted 26.10.0 release reference while preserving the existing vulnerability details and metadata, with no active review issues identified.
No open issues 🎉
What changed in this PR
This pull request adds the official Twisted 26.10.0 stable-release reference to the DNS response-spoofing security advisory, improving remediation traceability while preserving the existing vulnerability details and affected-version ranges.
Changes:
- Added the Twisted 26.10.0 stable release URL to the advisory references.
- Preserved existing metadata, references, severity, and version ranges.
- Moderate issue: Update the top-level
modifiedtimestamp to reflect this advisory change.
| File | Summary |
|---|---|
advisories/github-reviewed/2026/10/GHSA-jj36-9pvh-vj5r/GHSA-jj36-9pvh-vj5r.json |
Adds the official Twisted 26.10.0 stable-release reference. The modified value should be bumped so OSV consumers detect the updated record. |
Review effort: Lite (auto)
Updates
Comments
Added a reference to the official Twisted 26.10.0 stable release, published on October 30, 2026, which documents the DNS response-source validation fix associated with CVE-2026-83813 (GHSA-jj36-9pvh-vj5r).
The existing references include the upstream security advisory, NVD entry, fix pull request, fix commit, and 26.10.0 release candidate. Adding the stable-release reference provides a direct upstream source for the final security release and improves remediation traceability.
All existing references and advisory details have been preserved. No changes were made to the vulnerability description, affected package, vulnerable or patched version ranges, source code location, or CVSS vector.