VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

qutebrowser: vulnerability history, versions and safety

qutebrowser is a package in the PyPI ecosystem. Vulert records 8 vulnerabilities for it across 99 releases, from Jun 2018 to Oct 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H2 M1 L1 U4
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 qutebrowser vulnerabilities

Vulert verdict on qutebrowser 3.7.0 i

Updated on 23 Oct 2026

Action needed: 3.7.0 has 4 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 72/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 3.7.0 — affected i
  • Vulnerabilities on record 8 over 3 years · 0 in the last year i
  • Latest disclosure 22 Oct 2021 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Last release 6 months ago i
  • Licence GPL-3.0-or-later 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 qutebrowser, 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
3.7.0 03 Apr 2026 U4 GPL-3.0-or-later Yes Details →
3.6.3 30 Nov 2025 U4 GPL-3.0-or-later Yes Details →
3.6.2 27 Nov 2025 U4 GPL-3.0-or-later Yes Details →
3.6.1 03 Nov 2025 U4 GPL-3.0-or-later Yes Details →
3.6.0 24 Oct 2025 U4 GPL-3.0-or-later Yes Details →
3.5.1 05 Jun 2025 U4 GPL-3.0-or-later Yes Details →
3.5.0 12 Apr 2025 U4 GPL-3.0-or-later Yes Details →
3.4.0 14 Dec 2024 U4 non-standard Yes Details →
3.3.1 12 Oct 2024 U4 non-standard Yes Details →
3.3.0 12 Oct 2024 U4 non-standard Yes Details →
3.2.1 25 Jun 2024 U4 non-standard Yes Details →
3.2.0 03 Jun 2024 U4 non-standard Yes Details →
3.1.0 08 Dec 2023 U4 non-standard Yes Details →
3.0.2 19 Oct 2023 U4 non-standard Yes Details →
3.0.1 19 Oct 2023 U4 non-standard Yes Details →
3.0.0 18 Aug 2023 U4 non-standard Yes Details →
2.5.4 13 Mar 2023 U4 non-standard Yes Details →
2.5.3 17 Feb 2023 U4 non-standard Yes Details →
2.5.2 22 Jun 2022 U4 non-standard Yes Details →
2.5.1 26 May 2022 U4 non-standard Yes Details →
2.5.0 01 Apr 2022 U4 non-standard Yes Details →
2.4.0 21 Oct 2021 U4 non-standard Yes Details →
2.3.1 28 Jul 2021 H1 U1 non-standard Yes Details →
2.3.0 28 Jun 2021 H1 U1 non-standard Yes Details →
2.2.3 01 Jun 2021 H1 U1 non-standard Yes Details →
2.2.2 20 May 2021 H1 U1 non-standard Yes Details →
2.2.1 29 Apr 2021 H1 U1 non-standard Yes Details →
2.2.0 13 Apr 2021 H1 U1 non-standard Yes Details →
2.1.1 01 Apr 2021 H1 U1 non-standard Yes Details →
2.1.0 12 Mar 2021 H1 U1 non-standard Yes Details →
2.0.2 04 Feb 2021 H1 U1 non-standard Yes Details →
2.0.1 28 Jan 2021 H1 U1 non-standard Yes Details →
2.0.0 28 Jan 2021 H1 U1 non-standard Yes Details →
1.14.1 04 Dec 2020 H1 non-standard Yes Details →
1.14.0 15 Oct 2020 H1 non-standard Yes Details →
1.13.1 17 Jul 2020 H1 non-standard Yes Details →
1.13.0 26 Jun 2020 H1 non-standard Yes Details →
1.12.0 01 Jun 2020 H1 non-standard Yes Details →
1.11.1 07 May 2020 H1 non-standard Yes Details →
1.11.0 27 Apr 2020 H1 L1 non-standard Yes Details →
1.10.2 17 Apr 2020 H1 L1 U1 non-standard Yes Details →
1.10.1 15 Feb 2020 H1 L1 U1 non-standard Yes Details →
1.10.0 02 Feb 2020 H1 L1 U1 non-standard Yes Details →
1.9.0 08 Jan 2020 H1 L1 U1 non-standard Yes Details →
1.8.3 05 Dec 2019 H1 L1 U1 non-standard Yes Details →
1.8.2 22 Nov 2019 H1 L1 U1 non-standard Yes Details →
1.8.1 27 Sep 2019 H1 L1 U1 non-standard Yes Details →
1.8.0 25 Sep 2019 H1 L1 U1 non-standard Yes Details →
1.7.0 18 Jul 2019 H1 L1 U2 non-standard Yes Details →
1.6.3 18 Jun 2019 L1 U2 non-standard Yes Details →
1.6.2 06 May 2019 L1 U2 non-standard Yes Details →
1.6.1 20 Mar 2019 L1 U2 non-standard Yes Details →
1.6.0 25 Feb 2019 L1 U2 non-standard Yes Details →
1.5.2 26 Oct 2018 L1 U2 non-standard Yes Details →
1.5.1 10 Oct 2018 L1 U2 non-standard Yes Details →
1.5.0 03 Oct 2018 L1 U2 non-standard Yes Details →
1.4.2 02 Sep 2018 L1 U2 non-standard Yes Details →
1.4.1 11 Jul 2018 L1 U2 non-standard Yes Details →
1.4.0 03 Jul 2018 H1 L1 U3 non-standard Yes Details →
1.3.3 21 Jun 2018 H1 L1 U3 non-standard Yes Details →
1.3.2 10 Jun 2018 H1 M1 L1 U4 non-standard Yes Details →
1.3.1 29 May 2018 H1 M1 L1 U4 non-standard Yes Details →
1.3.0 04 May 2018 H1 M1 L1 U4 non-standard Yes Details →
1.2.1 14 Mar 2018 H1 M1 L1 U4 non-standard Yes Details →
1.2.0 09 Mar 2018 H1 M1 L1 U4 non-standard Yes Details →
1.1.2 01 Mar 2018 H1 M1 L1 U4 non-standard Yes Details →
1.1.1 20 Jan 2018 H1 M1 L1 U4 non-standard Yes Details →
1.1.0 15 Jan 2018 H1 M1 L1 U4 non-standard Yes Details →
1.0.4 28 Nov 2017 H1 M1 L1 U4 non-standard Yes Details →
1.0.2 17 Oct 2017 H1 M1 L1 U4 non-standard Yes Details →
1.0.1 13 Oct 2017 H1 M1 L1 U4 non-standard Yes Details →
1.0.0 12 Oct 2017 H1 M1 L1 U4 non-standard Yes Details →
0.11.1 09 Oct 2017 H1 M1 L1 U4 non-standard Yes Details →
0.11.0 04 Jul 2017 H1 M1 L1 U4 non-standard Yes Details →
0.10.1 08 Mar 2017 H1 L1 U3 non-standard Yes Details →
0.10.0 25 Feb 2017 H1 L1 U3 non-standard Yes Details →
0.9.1 13 Jan 2017 H1 L1 U3 non-standard Yes Details →
0.9.0 28 Dec 2016 H1 L1 U3 non-standard Yes Details →
0.8.4 05 Nov 2016 H1 L1 U3 non-standard Yes Details →
0.8.3 05 Nov 2016 H1 L1 U3 non-standard Yes Details →
0.8.2 02 Aug 2016 H1 L1 U3 non-standard Yes Details →
0.8.1 27 Jul 2016 H1 L1 U3 non-standard Yes Details →
0.8.0 26 Jul 2016 H1 L1 U3 non-standard Yes Details →
0.7.0 10 Jun 2016 H1 L1 U3 non-standard Yes Details →
0.6.2 30 Apr 2016 H1 L1 U3 non-standard Yes Details →
0.6.1 10 Apr 2016 H1 L1 U3 non-standard Yes Details →
0.6.0 04 Apr 2016 H1 L1 U3 non-standard Yes Details →
0.5.1 18 Jan 2016 H1 L1 U3 non-standard Yes Details →
0.5.0 05 Jan 2016 H1 L1 U3 non-standard Yes Details →
0.4.1 30 Sep 2015 H1 L1 U3 non-standard Yes Details →
0.4.0 11 Sep 2015 H1 L1 U3 non-standard Yes Details →
0.2.1 19 Apr 2015 H1 L1 U3 non-standard Yes Details →
0.1.4 19 Mar 2015 H1 L1 U3 non-standard Yes Details →
0.1.3 12 Feb 2015 H1 L1 U3 non-standard Yes Details →
0.1.2 09 Jan 2015 H1 L1 U3 non-standard Yes Details →
0.1.1 28 Dec 2014 H1 L1 U3 non-standard Yes Details →
0.1.0 14 Dec 2014 H1 L1 U3 non-standard Yes Details →
0.3.0.post2 — H1 L1 U4 non-standard Yes Details →
1.0.3.post1 — H1 M1 L1 U4 non-standard Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 4
  • 2020 2
  • 2021 2

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

03 Vulnerabilities

Recorded vulnerabilities for qutebrowser

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-41146: Arbitrary command execution on Windows via qutebrowserurl: URL handler 8.8 high 2.4.0 22 Oct 2021
CVE-2018-10895: qutebrowser - Cross-Site Request Forgery Vulnerability 8.8 high 1.4.1 10 Oct 2018
CVE-2018-1000559: qutebrowser Cross Site Scripting (XSS) Vulnerability 6.1 medium 1.3.3 13 Sep 2018
CVE-2020-11054: Incorrect Provision of Specified Functionality in qutebrowser 3.5 low 1.11.1 08 May 2020
CVE-2018-1000559: qutebrowser Cross Site Scripting (XSS) Vulnerability N/A unrated 5a7869f2feaa346853d2a85413d6527c87ef0d9f 26 Jun 2018

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 qutebrowser

Is qutebrowser safe to use?

Vulert records 8 vulnerabilities for qutebrowser in PyPI: 0 critical, 2 high, 1 medium and 1 low, plus 4 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 qutebrowser's Vulert package health score?

Vulert scores qutebrowser 72/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 qutebrowser affected?

Yes. 3.7.0, the version you would install today, has 4 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of qutebrowser should I use?

3.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 qutebrowser have?

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

0 vulnerabilities were recorded for qutebrowser in the last 12 months, and the oldest entry in this database dates to 26 Jun 2018. 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 qutebrowser 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 qutebrowser for upcoming vulnerabilities?

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