<?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://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-09T00:44:34.096205+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" 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://db.gcve.eu/vuln/cleanstart-2026-hj01174</id>
    <title>CLEANSTART-2026-HJ01174 — Security fix for GHSA-2mjx-qc3c-rqvc applied in: rustup 1.28.2-r3</title>
    <updated>2026-11-09T00:44:34.097399+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: rustup</p>
<p>Security vulnerability affects the rustup package. This issue is resolved in later releases. See references for vulnerability details.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cleanstart-2026-hj01174"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/rustsec-2026-0285</id>
    <title>RUSTSEC-2026-0285 — TLS 1.3 handshake messages incorrectly accepted across encryption level boundaries</title>
    <updated>2026-11-09T00:44:34.097455+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: rustls</p>
<p>Rustls accepted TLS 1.3 handshake messages sent at the wrong encryption level
when they followed a key-changing message in the same record. For example,
a plaintext `EncryptedExtensions` message packed into the same record as the
`ServerHello` was accepted.</p>
<p>RFC 8446 section 5.1 requires that handshake messages do not span key changes,
and that implementations terminate the connection with an "unexpected_message"
alert if they do.</p>
<p>The handshake transcript is still authenticated, so a network-position attacker
cannot use this to alter or complete a handshake; the practical effect is that
a peer could send handshake messages that should be encrypted in plaintext
without rustls rejecting the connection.</p>
<p>This is functionally the same bug as Go's
[GO-2026-4340](https://pkg.go.dev/vuln/GO-2026-4340) (CVE-2025-61730).</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/rustsec-2026-0285"/>
  </entry>
</feed>
