<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T21:08:44.459337+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2020-11054</id>
    <title>CVE-2020-11054 — Incorrect Provision of Specified Functionality in qutebrowser</title>
    <updated>2026-10-04T21:08:44.491910+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> qutebrowser</p>
<p>In qutebrowser versions less than 1.11.1, reloading a page with certificate errors shows a green URL. 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. This has been fixed in 1.11.1 and 1.12.0. All versions of qutebrowser are believed to be affected, though versions before v0.11.x couldn't be tested. Backported patches for older versions (greater than or equal to 1.4.0 and less than or equal to 1.10.2) are available, but no further releases are planned.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2020-11054"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-4rcq-jv2f-898j</id>
    <title>GHSA-4rcq-jv2f-898j — Incorrect Provision of Specified Functionality in qutebrowser</title>
    <updated>2026-10-04T21:08:44.491980+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: qutebrowser</p>
<p># Description</p>
<p>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.</p>
<p># Affected versions and patches</p>
<p>All versions of qutebrowser are believed to be affected, though versions before v0.11.x couldn't be tested.</p>
<p>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.</p>
<p># Mitigation</p>
<p>If you are unable to upgrade:</p>
<p>- 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</p>
<p># References</p>
<p>- 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)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-4rcq-jv2f-898j"/>
  </entry>
</feed>
