NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2018-10895 — qutebrowser

HIGHFix: qutebrowser/qutebrowser@43e58ac

CVE-2018-10895 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in qutebrowser. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for qutebrowser — see the affected versions and patch details below.

Qutebrowser CSRF Vulnerability

Also known asGHSA-wgmx-52ph-qqcwPYSEC-2018-27
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
2 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk
0.00%0.57%1.13%1.70%0.2%1.2%May 26Sep 26Nov 26

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

qutebrowser before version 1.4.1 is vulnerable to a cross-site request forgery flaw that allows websites to access 'qute://*' URLs. A malicious website could exploit this to load a 'qute://settings/set' URL, which then sets 'editor.command' to a bash script, resulting in arbitrary code execution.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIqutebrowserall versions1.4.1pip install --upgrade 'qutebrowser==1.4.1'

Affected Products

1 product · 1 configurations
Application
qutebrowserqutebrowser
< 1.4.1
range
Exploits & PoCs
2

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

    Update qutebrowser to 1.4.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-10895 is resolved across your whole dependency graph.

  3. 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

qutebrowser before version 1.4.1 is vulnerable to a cross-site request forgery flaw that allows websites to access 'qute://*' URLs. A malicious website could exploit this to load a 'qute://settings/set' URL, which then sets 'editor.command' to a bash script, resulting in arbitrary code execution.
O3 Security · Impact-Aware SCA

Is CVE-2018-10895 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2018-10895: qutebrowser RCE — Fixed in 1.4.1