Incorrect Provision of Specified Functionality in qutebrowser (CVE-2020-11054)

Why this deserves its current priority

CVSS is 3.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps qutebrowser (pypi). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
qutebrowserpypi	>=0 <1.11.1	1.11.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for qutebrowser.
Review the reported fix. Update qutebrowser to 1.11.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
May 8, 2020
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Aug 7, 2026

Sources and claim methodology

Upstream source description

# Description After a certificate error was overridden by the user, qutebrowser displays the URL as yellow (`colors.statusbar.url.warn.fg`). However, when the affected website was subsequently loaded again, the URL was mistakenly displayed as green (`colors.statusbar.url.success_https`). While the user already has seen a certificate error prompt at this point (or set `content.ssl_strict` to `false` which is not recommended), this could still provide a false sense of security. # Affected versions and patches All versions of qutebrowser are believed to be affected, though versions before v0.11.x couldn't be tested. The issue is fixed in qutebrowser v1.11.1 (pending release) and v1.12.0 (unreleased). Backported patches for older versions are available, but no further releases are planned. # Mitigation If you are unable to upgrade: - Treat any host with a certificate exception as insecure, ignoring the URL color - Or set `content.ssl_strict` to `True` (instead of `'ask'`), preventing certificate exceptions # References - qutebrowser issue: https://github.com/qutebrowser/qutebrowser/issues/5403 - Fix (master branch): https://github.com/qutebrowser/qutebrowser/commit/021ab572a319ca3db5907a33a59774f502b3b975 - Related issue for KDE Falkon: https://bugs.kde.org/show_bug.cgi?id=420902 - Related issue for eric6 Web Browser: https://tracker.die-offenbachs.homelinux.org/eric/issue328 (fixed in eric6 20.6)

Quoted source text, attributed separately from HOL analysis.