[PR #419] [MERGED] [Snyk] Security upgrade django from 3.1 to 3.1.1 #960

New issue

Closed

opened 2026-02-25 23:44:18 +03:00 by kerem · 0 comments

kerem commented

2026-02-25 23:44:18 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/healthchecks/healthchecks/pull/419
Author: @snyk-bot
Created: 9/2/2020
Status: ✅ Merged
Merged: 9/3/2020
Merged by: @cuu508

Base: master ← Head: snyk-fix-3b4d7e5e456fc8fadd61239890135796

📝 Commits (1)

c846260 fix: requirements.txt to reduce vulnerabilities

📊 Changes

1 file changed (+1 additions, -1 deletions)

View changed files

📝 requirements.txt (+1 -1)

📄 Description

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
- requirements.txt

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	651/1000 Why? Recently disclosed, Has a fix available, CVSS 7.3	Insecure Permissions SNYK-PYTHON-DJANGO-609368	`django:` `3.1 -> 3.1.1`	No	No Known Exploit
	706/1000 Why? Recently disclosed, Has a fix available, CVSS 8.4	Insecure Permissions SNYK-PYTHON-DJANGO-609369	`django:` `3.1 -> 3.1.1`	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/healthchecks/healthchecks/pull/419 **Author:** [@snyk-bot](https://github.com/snyk-bot) **Created:** 9/2/2020 **Status:** ✅ Merged **Merged:** 9/3/2020 **Merged by:** [@cuu508](https://github.com/cuu508) **Base:** `master` ← **Head:** `snyk-fix-3b4d7e5e456fc8fadd61239890135796` --- ### 📝 Commits (1) - [`c846260`](https://github.com/healthchecks/healthchecks/commit/c84626040cf303ff93f6e43215a99501c3f0b6ee) fix: requirements.txt to reduce vulnerabilities ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `requirements.txt` (+1 -1) </details> ### 📄 Description <h3>Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.</h3> #### Changes included in this PR - Changes to the following files to upgrade the vulnerable dependencies to a fixed version: - requirements.txt #### Vulnerabilities that will be fixed ##### By pinning: Severity | Priority Score (*) | Issue | Upgrade | Breaking Change | Exploit Maturity :-------------------------:|-------------------------|:-------------------------|:-------------------------|:-------------------------|:------------------------- ![high severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/h.png "high severity") | **651/1000** **Why?** Recently disclosed, Has a fix available, CVSS 7.3 | Insecure Permissions [SNYK-PYTHON-DJANGO-609368](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-609368) | `django:` `3.1 -> 3.1.1` | No | No Known Exploit ![high severity](https://res.cloudinary.com/snyk/image/upload/w_20,h_20/v1561977819/icon/h.png "high severity") | **706/1000** **Why?** Recently disclosed, Has a fix available, CVSS 8.4 | Insecure Permissions [SNYK-PYTHON-DJANGO-609369](https://snyk.io/vuln/SNYK-PYTHON-DJANGO-609369) | `django:` `3.1 -> 3.1.1` | No | No Known Exploit (*) Note that the real score may have changed since the PR was raised. Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded. Check the changes in this PR to ensure they won't cause issues with your project. ------------ **Note:** *You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.* For more information: <img src="https://api.segment.io/v1/pixel/track?data=eyJ3cml0ZUtleSI6InJyWmxZcEdHY2RyTHZsb0lYd0dUcVg4WkFRTnNCOUEwIiwiYW5vbnltb3VzSWQiOiI5ZjkzNDIzNy04NDFkLTQxNDgtODYxNi03MjRlM2JjNTc0YTkiLCJldmVudCI6IlBSIHZpZXdlZCIsInByb3BlcnRpZXMiOnsicHJJZCI6IjlmOTM0MjM3LTg0MWQtNDE0OC04NjE2LTcyNGUzYmM1NzRhOSJ9fQ==" width="0" height="0"/> 🧐 [View latest project report](https://app.snyk.io/org/cuu508/project/a62de668-9be4-47cc-b926-fa169a96d983) 🛠 [Adjust project settings](https://app.snyk.io/org/cuu508/project/a62de668-9be4-47cc-b926-fa169a96d983/settings) 📚 [Read more about Snyk's upgrade and patch logic](https://support.snyk.io/hc/en-us/articles/360003891078-Snyk-patches-to-fix-vulnerabilities) [//]: # (snyk:metadata:{"prId":"9f934237-841d-4148-8616-724e3bc574a9","dependencies":[{"name":"django","from":"3.1","to":"3.1.1"}],"packageManager":"pip","projectPublicId":"a62de668-9be4-47cc-b926-fa169a96d983","projectUrl":"https://app.snyk.io/org/cuu508/project/a62de668-9be4-47cc-b926-fa169a96d983?utm_source=github&utm_medium=fix-pr","type":"auto","patch":[],"vulns":["SNYK-PYTHON-DJANGO-609368","SNYK-PYTHON-DJANGO-609369"],"upgrade":[],"isBreakingChange":false,"env":"prod","prType":"fix","templateVariants":["updated-fix-title","priorityScore"],"priorityScoreList":[651,706]}) --- 🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.