starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Update Django to 5.2.7 #11714

New Issue
Closed
opened 2025-12-29 21:48:55 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:48:55 +01:00
Owner
Copy Link

Originally created by @stuntguy3000 on GitHub (Oct 13, 2025).

Originally assigned to: @jnovinger on GitHub.

NetBox version

v4.4.2

Feature type

Other

Proposed functionality

https://www.djangoproject.com/weblog/2025/oct/01/security-releases/

I am requesting Django is updated to 5.2.7 to address CVE-2025-59681.

Use case

Addressing upstream security issue. Enterprise environments where package management scanning are used, may alarm/alert/block the current installation of NetBox, due to Django v5.2.6's recently released critical CVE.

Database changes

None

External dependencies

Django v5.2.7

Originally created by @stuntguy3000 on GitHub (Oct 13, 2025). Originally assigned to: @jnovinger on GitHub. ### NetBox version v4.4.2 ### Feature type Other ### Proposed functionality https://www.djangoproject.com/weblog/2025/oct/01/security-releases/ I am requesting Django is updated to 5.2.7 to address **CVE-2025-59681**. ### Use case Addressing upstream security issue. Enterprise environments where package management scanning are used, may alarm/alert/block the current installation of NetBox, due to Django v5.2.6's recently released critical CVE. ### Database changes None ### External dependencies Django v5.2.7
adam added the status: acceptedtype: housekeeping labels 2025-12-29 21:48:55 +01:00
adam closed this issue 2025-12-29 21:48:55 +01:00
adam commented 2025-12-29 21:48:55 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Oct 13, 2025):

Thanks for the report, @stuntguy3000 . Normally, we address dependency updates as part of our release process, not usually as standalone work. The next patch release, v4.4.3, is scheduled to be released on Tuesday (Oct. 14, 2025) and would include Django 5.2.7.

However, you make a good point about enterprise scanning tools flagging the vulnerable Django version. While the vulnerabilities themselves don't affect NetBox (see note below), the alerts can create friction in deployment pipelines and require manual verification/overrides. That said, this may not end up being merged until Tuesday anyway, since all PRs require approval from a maintainer other than the author.

Note: Neither of these particular vulnerabilities do or will affect NetBox. The SQL injection vulnerability only affects MySQL and MariaDB, while NetBox requires and only uses PostgreSQL. The directory-traversal vulnerability requires the use of startapp or startproject, which the project has no need for between now and v4.4.3.

@jnovinger commented on GitHub (Oct 13, 2025): Thanks for the report, @stuntguy3000 . Normally, we address dependency updates as part of our [release process](https://netboxlabs.com/docs/netbox/development/release-checklist/#minor-version-releases), not usually as standalone work. The next patch release, v4.4.3, is scheduled to be released on Tuesday (Oct. 14, 2025) and would include Django 5.2.7. However, you make a good point about enterprise scanning tools flagging the vulnerable Django version. While the vulnerabilities themselves don't affect NetBox (see note below), the alerts can create friction in deployment pipelines and require manual verification/overrides. That said, this may not end up being merged until Tuesday anyway, since all PRs require approval from a maintainer other than the author. **Note**: Neither of these particular vulnerabilities do or will affect NetBox. The SQL injection vulnerability only affects MySQL and MariaDB, while NetBox requires and only uses PostgreSQL. The directory-traversal vulnerability requires the use of `startapp` or `startproject`, which the project has no need for between now and v4.4.3.
adam commented 2025-12-29 21:48:56 +01:00
Author
Owner
Copy Link

@stuntguy3000 commented on GitHub (Oct 13, 2025):

Thanks for the report, @stuntguy3000 . Normally, we address dependency updates as part of our release process, not usually as standalone work. The next patch release, v4.4.3, is scheduled to be released on Tuesday (Oct. 14, 2025) and would include Django 5.2.7.

However, you make a good point about enterprise scanning tools flagging the vulnerable Django version. While the vulnerabilities themselves don't affect NetBox (see note below), the alerts can create friction in deployment pipelines and require manual verification/overrides. That said, this may not end up being merged until Tuesday anyway, since all PRs require approval from a maintainer other than the author.

Note: Neither of these particular vulnerabilities do or will affect NetBox. The SQL injection vulnerability only affects MySQL and MariaDB, while NetBox requires and only uses PostgreSQL. The directory-traversal vulnerability requires the use of startapp or startproject, which the project has no need for between now and v4.4.3.

Not a worry, appreciate the quick response! Manually changing the version in the requirements file is a good workaround, until the next release.

@stuntguy3000 commented on GitHub (Oct 13, 2025): > Thanks for the report, [@stuntguy3000](https://github.com/stuntguy3000) . Normally, we address dependency updates as part of our [release process](https://netboxlabs.com/docs/netbox/development/release-checklist/#minor-version-releases), not usually as standalone work. The next patch release, v4.4.3, is scheduled to be released on Tuesday (Oct. 14, 2025) and would include Django 5.2.7. > > However, you make a good point about enterprise scanning tools flagging the vulnerable Django version. While the vulnerabilities themselves don't affect NetBox (see note below), the alerts can create friction in deployment pipelines and require manual verification/overrides. That said, this may not end up being merged until Tuesday anyway, since all PRs require approval from a maintainer other than the author. > > **Note**: Neither of these particular vulnerabilities do or will affect NetBox. The SQL injection vulnerability only affects MySQL and MariaDB, while NetBox requires and only uses PostgreSQL. The directory-traversal vulnerability requires the use of `startapp` or `startproject`, which the project has no need for between now and v4.4.3. Not a worry, appreciate the quick response! Manually changing the version in the requirements file is a good workaround, until the next release.
adam commented 2025-12-29 21:48:56 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Oct 14, 2025):

This shipped in v4.4.3 today: https://github.com/netbox-community/netbox/releases/tag/v4.4.3

@jnovinger commented on GitHub (Oct 14, 2025): This shipped in v4.4.3 today: https://github.com/netbox-community/netbox/releases/tag/v4.4.3
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: housekeeping
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11714
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?