Skip to content

deps: update django requirement from <5.3,>=5.2.15 to >=6.0.7,<6.1 - #14

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/django-gte-6.0.7-and-lt-6.1
Open

deps: update django requirement from <5.3,>=5.2.15 to >=6.0.7,<6.1#14
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/django-gte-6.0.7-and-lt-6.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 20, 2026

Copy link
Copy Markdown
Contributor

Updates the requirements on django to permit the latest version.

Commits
  • e2a4246 [6.0.x] Bumped version for 6.0.7 release.
  • a5de13f [6.0.x] Fixed CVE-2026-53878 -- Prevented newlines from being accepted in Dom...
  • 38dfbd2 [6.0.x] Fixed CVE-2026-53877 -- Prevented heap buffer over-read when creating...
  • 64f9a2b [6.0.x] Fixed CVE-2026-48588 -- Prevented caching of responses that set cooki...
  • c26957a [6.0.x] Fixed flatpages synopsis in docs.
  • 0b60f44 [6.0.x] Added FILE_UPLOAD_DIRECTORY_PERMISSIONS to docs settings index.
  • d928e30 [6.0.x] Fixed #37172 -- Linked to upload handlers section in FILE_UPLOAD_* se...
  • e18935c [6.0.x] Fixed #37158 -- Reordered the contribution checklist sections.
  • 490eb9c [6.0.x] Fixed document referenced in multiple toctrees warning in docs/intern...
  • 748a9b5 [6.0.x] Fixed duplicate target name in docs/internals/howto-release-django.txt.
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Updates the requirements on [django](https://github.com/django/django) to permit the latest version.
- [Commits](django/django@5.2.15...6.0.7)

---
updated-dependencies:
- dependency-name: django
  dependency-version: 6.0.7
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Jul 20, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

ebrandi added a commit that referenced this pull request Jul 31, 2026
…#14, #15, #16)

Three alerts, one real bug and two guards the scanner cannot see.

#16 is not an open redirect — the path comes from reverse() and the term only ever lands
after the `?`, so neither scheme nor host is reachable. It was still wrong: the term was
interpolated with no encoding, so an `&`, `#` or `=` in a free-text search added parameters
or truncated the URL at a fragment, quietly changing what the officer had typed. Now
urlencoded.

#15 and #14 are genuine false positives, and both are now pinned rather than dismissed.
The adversary redirect is safe because is_valid_kind() is a strict allowlist that raises
Http404 before any use of the value — which matters more than it looks, because Django's
resolve_url falls back to treating the argument as a literal URL when reverse() raises, and
`killboard:adversary_...` would then read as a custom scheme. The stream handler returns
str(exc) on a TopicError, a project ValueError carrying messages we author; no traceback or
internal state reaches the client, and the echoed topic is now bounded so a caller cannot
have an arbitrarily long string reflected.

A dismissal comment would have satisfied the scanner and left both guards deletable. The
tests fail if either is removed, which is the difference between recording that the code is
safe and keeping it that way.
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.

0 participants