Follow-up on GHSA-ggq6-wv5j-cpfg
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.3k
- Forks
- 836
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 1
Description
Describe the bug
Dear Mantainers，
Just wanted to gently follow up on the security advisory (GHSA-ggq6-wv5j-cpfg) I submitted about two weeks ago.
I understand you're likely busy, so I wanted to make sure this didn't fall through the cracks. If you have any questions about the report or need more details to reproduce the issue, please let me know. I'm happy to help.
Thanks for your time!
Reproduction steps
Details are included in the advisory (GHSA-ggq6-wv5j-cpfg)
Expected behavior
Validate this bug. And if this bug truly exists, repair it.
Bandit version
1.9.1 (Default)
Python version
3.14 (Default)
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the details and reproduction steps in advisory GHSA-ggq6-wv5j-cpfg, then validate the reported behavior against Bandit 1.9.1 with Python 3.14. Done means confirming whether the vulnerability exists and, if it does, repairing it so the reported behavior is no longer reproducible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100