VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

treq: vulnerability history, versions and safety

treq is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 18 releases, first recorded in Feb 2022. 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 H1 U1
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.

See all treq vulnerabilities

Vulert verdict on treq 26.7.0 i

Updated on 23 Oct 2026

Good news: 26.7.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 26.7.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 26.7.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 26.7.0 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 01 Feb 2022 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 52 packages i
  • Stars 604 i
  • OpenSSF scorecard 6/10 i
  • Last release 3 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for treq, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
26.7.0 02 Jul 2026 none MIT — Details →
25.5.0 03 Jun 2025 none MIT — Details →
24.9.1 19 Sep 2024 none non-standard — Details →
24.9.0 18 Sep 2024 none non-standard — Details →
23.11.0 04 Nov 2023 none non-standard — Details →
22.2.0 09 Feb 2022 none non-standard — Details →
22.1.0 30 Jan 2022 none non-standard — Details →
21.5.0 24 May 2021 H1 U1 non-standard Yes Details →
21.1.0 15 Jan 2021 H1 U1 non-standard Yes Details →
20.9.0 27 Sep 2020 H1 non-standard Yes Details →
20.9.0rc1 27 Sep 2020 H1 non-standard Yes Details →
20.4.1 17 Apr 2020 H1 non-standard Yes Details →
20.3.0 16 Mar 2020 H1 non-standard Yes Details →
20.3.0rc1 16 Mar 2020 H1 non-standard Yes Details →
18.6.0 29 Jun 2018 H1 non-standard Yes Details →
17.8.0 19 Aug 2017 H1 non-standard Yes Details →
17.7.0 01 Aug 2017 H1 non-standard Yes Details →
17.3.1 28 Mar 2017 H1 non-standard Yes Details →
17.3.0 28 Mar 2017 H1 non-standard Yes Details →
16.12.0 14 Dec 2016 H1 non-standard Yes Details →
15.1.0 18 Dec 2015 H1 non-standard Yes Details →
15.0.0 05 Feb 2015 H1 non-standard Yes Details →
0.2.1 06 Mar 2014 H1 non-standard Yes Details →
0.2.0 30 Apr 2013 H1 non-standard Yes Details →
0.1.0 28 Dec 2012 H1 non-standard Yes Details →

All 25 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 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 treq

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2022-23607: Unsafe handling of user-specified cookies in treq 6.5 high 22.1.0 01 Feb 2022
CVE-2022-23607: treq - HTTP Library Supercookie Vulnerability N/A unrated 22.1.0 01 Feb 2022

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 treq

Is treq safe to use?

Vulert records 2 vulnerabilities for treq in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 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.

What is treq's Vulert package health score?

Vulert scores treq 83/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of treq affected?

No. 26.7.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of treq should I use?

26.7.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does treq have?

2 vulnerabilities are recorded for treq in the PyPI ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 treq vulnerabilities disclosed?

0 vulnerabilities were recorded for treq in the last 12 months, and the oldest entry in this database dates to 01 Feb 2022. 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 treq 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 treq for upcoming vulnerabilities?

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