VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

gpt-researcher: vulnerability history, versions and safety

gpt-researcher is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 8 releases, from Jul 2026 to Oct 2026. 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 C1 U1
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all gpt-researcher vulnerabilities

Vulert verdict on gpt-researcher 0.16.1 i

Updated on 23 Oct 2026

Careful: 0.16.1 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.16.1 — affected i
  • Vulnerabilities on record 2 over 1 year · 2 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 2 i
  • Depended on by 5 packages i
  • Stars 30,179 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 gpt-researcher, 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
0.16.1 26 Sep 2026 C1 U1 MIT No Details →
0.16.0 18 Jul 2026 C1 U1 MIT No Details →
0.15.1 28 May 2026 C1 U1 MIT No Details →
0.15.0 28 May 2026 C1 U1 MIT No Details →
0.14.8 13 Mar 2026 C1 U1 MIT No Details →
0.14.7 01 Mar 2026 C1 U1 MIT No Details →
0.14.6 29 Jan 2026 C1 U1 MIT No Details →
0.14.5 07 Nov 2025 C1 U1 MIT No Details →
0.14.4 17 Sep 2025 none MIT — Details →
0.14.3 08 Aug 2025 none MIT — Details →
0.14.2 19 Jul 2025 none MIT — Details →
0.14.1 04 Jul 2025 none MIT — Details →
0.14.0 06 Jun 2025 none MIT — Details →
0.13.5 06 Jun 2025 none MIT — Details →
0.13.4 01 Jun 2025 none MIT — Details →
0.13.3 26 Apr 2025 none MIT — Details →
0.13.2 26 Apr 2025 none MIT — Details →
0.13.1 26 Apr 2025 none MIT — Details →
0.13.0 26 Apr 2025 none MIT — Details →
0.12.19 04 Apr 2025 none MIT — Details →
0.12.18 04 Apr 2025 none MIT — Details →
0.12.17 31 Mar 2025 none MIT — Details →
0.12.16 29 Mar 2025 none MIT — Details →
0.12.14 27 Mar 2025 none MIT — Details →
0.12.12 09 Mar 2025 none MIT — Details →
0.12.11 09 Mar 2025 none MIT — Details →
0.12.10 09 Mar 2025 none MIT — Details →
0.12.9 09 Mar 2025 none MIT — Details →
0.12.8 01 Mar 2025 none MIT — Details →
0.12.7 27 Feb 2025 none MIT — Details →
0.12.6 26 Feb 2025 none MIT — Details →
0.12.5 25 Feb 2025 none MIT — Details →
0.12.4 24 Feb 2025 none MIT — Details →
0.12.3 24 Feb 2025 none MIT — Details →
0.12.2 24 Feb 2025 none MIT — Details →
0.12.1 22 Feb 2025 none MIT — Details →
0.12.0 22 Feb 2025 none MIT — Details →
0.11.9 22 Feb 2025 none MIT — Details →
0.11.8 21 Feb 2025 none MIT — Details →
0.11.7 21 Feb 2025 none MIT — Details →
0.11.6 21 Feb 2025 none MIT — Details →
0.11.5 21 Feb 2025 none MIT — Details →
0.11.4 21 Feb 2025 none MIT — Details →
0.11.3 21 Feb 2025 none MIT — Details →
0.11.2 21 Feb 2025 none MIT — Details →
0.11.1 17 Feb 2025 none MIT — Details →
0.11.0 12 Feb 2025 none MIT — Details →
0.10.11 05 Jan 2025 none MIT — Details →
0.10.10 29 Dec 2024 none MIT — Details →
0.10.9 21 Dec 2024 none MIT — Details →
0.10.8 18 Dec 2024 none MIT — Details →
0.10.7 18 Dec 2024 none MIT — Details →
0.10.6 17 Dec 2024 none MIT — Details →
0.10.5 15 Dec 2024 none MIT — Details →
0.10.4 14 Dec 2024 none MIT — Details →
0.10.3 03 Nov 2024 none MIT — Details →
0.10.2 23 Oct 2024 none MIT — Details →
0.9.9 18 Oct 2024 none MIT — Details →
0.9.8 15 Oct 2024 none MIT — Details →
0.9.7 14 Oct 2024 none MIT — Details →
0.9.6 14 Sep 2024 none MIT — Details →
0.9.5 07 Sep 2024 none MIT — Details →
0.9.4 06 Sep 2024 none MIT — Details →
0.9.3 04 Sep 2024 none MIT — Details →
0.9.2 04 Sep 2024 none MIT — Details →
0.9.1 26 Aug 2024 none MIT — Details →
0.9.0 23 Aug 2024 none MIT — Details →
0.8.8 16 Aug 2024 none MIT — Details →
0.8.7 15 Aug 2024 none MIT — Details →
0.8.6 15 Aug 2024 none MIT — Details →
0.8.5 12 Aug 2024 none MIT — Details →
0.8.4 06 Aug 2024 none MIT — Details →
0.8.3 04 Aug 2024 none MIT — Details →
0.8.2 19 Jul 2024 none MIT — Details →
0.8.1 18 Jul 2024 none MIT — Details →
0.8.0 15 Jul 2024 none MIT — Details →
0.7.1 06 Jul 2024 none MIT — Details →
0.7.0 23 Jun 2024 none MIT — Details →
0.6.9 20 Jun 2024 none MIT — Details →
0.6.8 19 Jun 2024 none MIT — Details →
0.6.7 18 Jun 2024 none MIT — Details →
0.6.6 18 Jun 2024 none MIT — Details →
0.6.5 18 Jun 2024 none MIT — Details →
0.6.4 15 Jun 2024 none MIT — Details →
0.6.3 12 Jun 2024 none MIT — Details →
0.6.2 10 Jun 2024 none MIT — Details →
0.6.1 30 May 2024 none MIT — Details →
0.6.0 27 May 2024 none MIT — Details →
0.5.4 25 May 2024 none MIT — Details →
0.5.3 23 May 2024 none MIT — Details →
0.5.2 23 May 2024 none MIT — Details →
0.5.1 23 May 2024 none MIT — Details →
0.4.5 14 May 2024 none MIT — Details →
0.4.4 14 May 2024 none MIT — Details →
0.4.3 12 May 2024 none MIT — Details →
0.4.2 12 May 2024 none MIT — Details →
0.4.1 12 May 2024 none MIT — Details →
0.4.0 10 May 2024 none MIT — Details →
0.3.5 09 May 2024 none MIT — Details →
0.3.4 09 May 2024 none MIT — Details →
0.3.3 09 May 2024 none — — Details →
0.3.2 09 May 2024 none — — Details →
0.3.1 09 May 2024 none — — Details →
0.3.0 05 May 2024 none — — Details →
0.2.9 25 Apr 2024 none — — Details →
0.2.8 25 Apr 2024 none — — Details →
0.2.7 25 Apr 2024 none — — Details →
0.2.6 12 Apr 2024 none — — Details →
0.2.5 12 Apr 2024 none — — Details →
0.2.4 12 Apr 2024 none — — Details →
0.2.2 12 Apr 2024 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for gpt-researcher

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-65720: GPT Researcher Remote Command Execution Vulnerability 9.8 critical No fix published 16 Jul 2026
CVE-2025-65720: gpt-researcher Remote Command Execution Vulnerability 9.8 critical No fix published 15 Oct 2026

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 gpt-researcher

Is gpt-researcher safe to use?

Vulert records 2 vulnerabilities for gpt-researcher in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is gpt-researcher's Vulert package health score?

Vulert scores gpt-researcher 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of gpt-researcher affected?

Yes. 0.16.1, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of gpt-researcher should I use?

0.16.1 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 gpt-researcher have?

2 vulnerabilities are recorded for gpt-researcher in the PyPI ecosystem: 1 critical, 0 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 gpt-researcher vulnerabilities disclosed?

2 vulnerabilities were recorded for gpt-researcher in the last 12 months, and the oldest entry in this database dates to 16 Jul 2026. 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 gpt-researcher 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 gpt-researcher for upcoming vulnerabilities?

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