Skip to content

[Snyk] Security upgrade pyasn1 from 0.5.1 to 0.6.2#423

Open
ra100 wants to merge 1 commit intomasterfrom
snyk-fix-469e2b99691526f64aa1c819ffe047ec
Open

[Snyk] Security upgrade pyasn1 from 0.5.1 to 0.6.2#423
ra100 wants to merge 1 commit intomasterfrom
snyk-fix-469e2b99691526f64aa1c819ffe047ec

Conversation

@ra100
Copy link
Owner

@ra100 ra100 commented Jan 20, 2026

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the pip dependencies of this project.

Snyk changed the following file(s):

  • lambda/requirements.txt
⚠️ Warning
sa 4.9.1 requires pyasn1, which is not installed.
cfn-lint 0.79.11 has requirement aws-sam-translator>=1.73.0, but you have aws-sam-translator 1.71.0.
botocore 1.33.13 has requirement urllib3<1.27,>=1.25.4; python_version < "3.10", but you have urllib3 2.0.7.
aws-sam-cli 1.95.0 requires ruamel-yaml, which is not installed.
aws-sam-cli 1.95.0 has requirement cookiecutter~=2.1.1, but you have cookiecutter 2.6.0.

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • 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 affected dependencies could be upgraded.

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
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

The following vulnerabilities are fixed by pinning transitive dependencies:
- https://snyk.io/vuln/SNYK-PYTHON-PYASN1-15032639
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.

2 participants