Vulnerability Database · Alpine · Package report

py3-requests: vulnerability history, versions and safety

py3-requests is a package in the Alpine ecosystem. Vulert records 2 vulnerabilities for it across 60 releases, first recorded in May 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on py3-requests i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 20 May 2024. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 2 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 20 May 2024 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for py3-requests, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
2.31.0-r0 U2 Yes Details →
2.30.0-r0 U2 Yes Details →
2.29.0-r0 U2 Yes Details →
2.28.2-r1 U2 Yes Details →
2.28.2-r0 U2 Yes Details →
2.28.1-r2 U2 Yes Details →
2.28.1-r1 U2 Yes Details →
2.28.1-r0 U2 Yes Details →
2.27.1-r0 U2 Yes Details →
2.26.0-r2 U2 Yes Details →
2.26.0-r1 U2 Yes Details →
2.26.0-r0 U2 Yes Details →
2.25.1-r4 U2 Yes Details →
2.25.1-r3 U2 Yes Details →
2.25.1-r2 U2 Yes Details →
2.25.1-r1 U2 Yes Details →
2.25.1-r0 U2 Yes Details →
2.25.0-r1 U2 Yes Details →
2.25.0-r0 U2 Yes Details →
2.24.0-r3 U2 Yes Details →
2.24.0-r2 U2 Yes Details →
2.24.0-r1 U2 Yes Details →
2.24.0-r0 U2 Yes Details →
2.23.0-r0 U2 Yes Details →
2.22.0-r1 U2 Yes Details →
2.22.0-r0 U2 Yes Details →
2.21.0-r6 U2 Yes Details →
2.21.0-r5 U2 Yes Details →
2.21.0-r4 U2 Yes Details →
2.21.0-r3 U2 Yes Details →
2.21.0-r2 U2 Yes Details →
2.21.0-r1 U2 Yes Details →
2.21.0-r0 U2 Yes Details →
2.19.1-r0 U2 Yes Details →
2.18.4-r0 U2 Yes Details →
2.18.3-r0 U2 Yes Details →
2.18.2-r0 U2 Yes Details →
2.18.1-r1 U2 Yes Details →
2.18.1-r0 U2 Yes Details →
2.17.3-r0 U2 Yes Details →
2.16.5-r0 U2 Yes Details →
2.13.0-r0 U2 Yes Details →
2.12.4-r1 U2 Yes Details →
2.12.4-r0 U2 Yes Details →
2.11.1-r1 U2 Yes Details →
2.11.1-r0 U2 Yes Details →
2.11.0-r0 U2 Yes Details →
2.10.0-r0 U2 Yes Details →
2.9.1-r0 U2 Yes Details →
2.8.1-r0 U2 Yes Details →
2.7.0-r0 U2 Yes Details →
2.6.0-r0 U2 Yes Details →
2.5.2-r0 U2 Yes Details →
2.5.1-r0 U2 Yes Details →
2.4.3-r0 U2 Yes Details →
2.3.0-r0 U2 Yes Details →
2.0.0-r0 U2 Yes Details →
1.2.3-r0 U2 Yes Details →
1.1.0-r0 U2 Yes Details →
1.0.4-r0 U2 Yes Details →

Newest 60 of 60 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 2 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for py3-requests

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About py3-requests

Is py3-requests safe to use?

Vulert records 2 vulnerabilities for py3-requests in Alpine: 0 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does py3-requests have?

2 vulnerabilities are recorded for py3-requests in the Alpine ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new py3-requests vulnerabilities disclosed?

0 vulnerabilities were recorded for py3-requests in the last 12 months, and the oldest entry in this database dates to 20 May 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of py3-requests are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor py3-requests for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the py3-requests version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.