<?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-02T13:44:08.414427+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/euvd-2026-88697</id>
    <title>EUVD-2026-88697</title>
    <updated>2026-10-02T13:44:08.418193+00:00</updated>
    <content>EUVD-2026-88697</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-88697"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2016-10931</id>
    <title>fkie_cve-2016-10931</title>
    <updated>2026-10-02T13:44:08.418233+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An issue was discovered in the openssl crate before 0.9.0 for Rust. There is an SSL/TLS man-in-the-middle vulnerability because certificate verification is off by default and there is no API for hostname verification.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2016-10931"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-34p9-f4q3-c4r7</id>
    <title>GHSA-34p9-f4q3-c4r7 — Improper Certificate Validation in openssl</title>
    <updated>2026-10-02T13:44:08.418286+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: openssl</p>
<p>All versions of rust-openssl prior to 0.9.0 contained numerous insecure defaults including off-by-default certificate verification and no API to perform hostname verification. Unless configured correctly by a developer, these defaults could allow an attacker to perform man-in-the-middle attacks. The problem was addressed in newer versions by enabling certificate verification by default and exposing APIs to perform hostname verification. Use the SslConnector and SslAcceptor types to take advantage of these new features (as opposed to the lower-level SslContext type).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-34p9-f4q3-c4r7"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2016-10931</id>
    <title>gsd-2016-10931</title>
    <updated>2026-10-02T13:44:08.418350+00:00</updated>
    <content>gsd-2016-10931</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2016-10931"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rustsec-2016-0001</id>
    <title>RUSTSEC-2016-0001 — SSL/TLS MitM vulnerability due to insecure defaults</title>
    <updated>2026-10-02T13:44:08.418375+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: openssl</p>
<p>All versions of rust-openssl prior to 0.9.0 contained numerous insecure defaults
including off-by-default certificate verification and no API to perform hostname
verification.</p>
<p>Unless configured correctly by a developer, these defaults could allow an attacker
to perform man-in-the-middle attacks.</p>
<p>The problem was addressed in newer versions by enabling certificate verification
by default and exposing APIs to perform hostname verification. Use the
`SslConnector` and `SslAcceptor` types to take advantage of these new features
(as opposed to the lower-level `SslContext` type).</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rustsec-2016-0001"/>
  </entry>
</feed>
