<?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-15T00:50:36.492002+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-2026-34183</id>
    <title>CVE-2026-34183 — Unbounded Memory Growth in the QUIC PATH_CHALLENGE Handler</title>
    <updated>2026-10-15T00:50:36.521763+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> OpenSSL</p>
<p>Issue summary: Remote peer may exhaust heap memory of the QUIC
server or client by flooding it with packets containing PATH_CHALLENGE
frames.</p>
<p>Impact summary: A malicious remote peer can cause an unbounded
memory allocation which can lead to an abnormal termination of the
application acting as a QUIC client or server and a Denial of Service.</p>
<p>A remote peer may exhaust heap memory by flooding the local
QUIC stack with PATH_CHALLENGE frames. The local QUIC stack
allocates a PATH_RESPONSE frame for every PATH_CHALLENGE it receives.
The allocated PATH_RESPONSE frame gets freed only when the remote
peer acknowledges reception of the PATH_RESPONSE frame which will
not be done by a malicious peer.</p>
<p>The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by
this issue. The QUIC stack is outside of OpenSSL FIPS module
boundary.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-34183"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/usn-8414-1</id>
    <title>USN-8414-1 — openssl vulnerabilities</title>
    <updated>2026-10-15T00:50:36.521848+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: openssl, Ubuntu:24.04:LTS: openssl, Ubuntu:25.10: openssl, Ubuntu:26.04:LTS: openssl</p>
<p>Frank Buss discovered that OpenSSL had a heap buffer over-read in ASN.1
content parsing. An attacker could possibly use this issue to cause OpenSSL
to crash, resulting in a denial of service, or obtain sensitive
information. (CVE-2026-34180)</p>
<p>Pavol Zacik and Alex Gaynor discovered that OpenSSL incorrectly accepted
PKCS#12 files with short HMAC keys when using PBMAC1. An attacker could
possibly use this issue to bypass integrity checks. This issue only
affected Ubuntu 25.10 and Ubuntu 26.04 LTS. (CVE-2026-34181)</p>
<p>Asim Viladi Oglu Manizada and Alex Gaynor discovered that OpenSSL could
accept forged CMS AuthEnvelopedData messages. An attacker could possibly
use this issue to bypass message authentication checks. (CVE-2026-34182)</p>
<p>Abhinav Agarwal discovered that OpenSSL had unbounded memory growth in the
QUIC PATH_CHALLENGE handler. A remote attacker could possibly use this
issue to cause OpenSSL to use excessive resources, leading to a denial of
service. This issue only affected Ubuntu 25.10 and Ubuntu 26.04 LTS.
(CVE-2026-34183)</p>
<p>Sunwoo Lee, Hyuk Lim, and Seunghyun Yoon discovered that OpenSSL had a NULL
pointer dereference in QUIC server initial packet handling. A remote
attacker could possibly use this issue to cause OpenSSL to crash, resulting
in a denial of service. This issue only affected Ubuntu 25.10 and Ubuntu
26.04 LTS. (CVE-2026-42764)</p>
<p>Mayank Jangid, Kushal Khemka, Hari Priandana, Bhabani Sankar Das, and Qifan
Zhang discovered that OpenSSL had a possible NULL derefe…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/usn-8414-1"/>
  </entry>
</feed>
