Skip to content

bump django #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
heliocodacy wants to merge 1 commit into
base: master
Choose a base branch
from
Open

bump django #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion python/requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
flask==1.0.2
django==1.11.29
django==4.2.24

Check notice on line 2 in python/requirements.txt

View check run for this annotation

Codacy Production / Codacy Static Code Analysis

python/requirements.txt#L2 

Insecure dependency pypi/django@4.2.24 (CVE-2025-59682: django: Potential partial directory-traversal via archive.extract()) (update to 4.2.25)

@codacy-production codacy-production Bot Nov 4, 2025

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ℹ️ Codacy found a minor Security issue: Insecure dependency pypi/django@4.2.24 (CVE-2025-59682: django: Potential partial directory-traversal via archive.extract()) (update to 4.2.25)

The issue identified by the Trivy linter is a security vulnerability in Django version 4.2.24, specifically a potential partial directory-traversal vulnerability that could be exploited via the archive.extract() method. This vulnerability is classified under CVE-2025-59682. To mitigate this security risk, it is recommended to update Django to a patched version, which is 4.2.25 or later.

To fix this issue, you simply need to update the version of Django in your requirements file. Here’s the code suggestion to apply the fix:

Suggested change
django==4.2.24
django==4.2.25

This comment was generated by an experimental AI tool.

requests==2.19.1