How severe is GHSA-4rcq-jv2f-898j?

GHSA-4rcq-jv2f-898j has a CVSS score of 3.5/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-4rcq-jv2f-898j?

GHSA-4rcq-jv2f-898j affects the following packages: qutebrowser (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-4rcq-jv2f-898j?

Update qutebrowser to 1.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rcq-jv2f-898j is resolved across your whole dependency graph.

How do I detect GHSA-4rcq-jv2f-898j in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for qutebrowser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-4rcq-jv2f-898j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-4rcq-jv2f-898j actively exploited in the wild?

No public exploit code has been indexed for GHSA-4rcq-jv2f-898j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-4rcq-jv2f-898j?

GHSA-4rcq-jv2f-898j has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 75th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-4rcq-jv2f-898j?

GHSA-4rcq-jv2f-898j is classified as CWE-684 (CWE-684). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-4rcq-jv2f-898j published, and has it been updated?

GHSA-4rcq-jv2f-898j was published on May 8, 2020 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

LOW severity

Incorrect Provision of Specified Functionality in qutebrowserGHSA-4rcq-jv2f-898j

LOWFix: qutebrowser/qutebrowser@021ab57

GHSA-4rcq-jv2f-898j is a low-severity (CVSS 3.5) CWE-684 vulnerability in qutebrowser. A fix is available for qutebrowser — see the affected versions and patch details below.

Also known asCVE-2020-11054PYSEC-2020-97

Published

May 8, 2020

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍qutebrowser

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`qutebrowser`	all versions	1.11.1`pip install --upgrade 'qutebrowser==1.11.1'`

Affected Products

2 products · 3 configurations

fedorafedoraproject

2 versions

3132

Application

qutebrowserqutebrowser

< 1.11.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for qutebrowser, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update qutebrowser to 1.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rcq-jv2f-898j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

# 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.1

O3 Security · Impact-Aware SCA

Is GHSA-4rcq-jv2f-898j in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works

Incorrect Provision of Specified Functionality in qutebrowserGHSA-4rcq-jv2f-898j

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Description

Affected versions and patches

Mitigation

References

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-4rcq-jv2f-898j in your dependencies?