<?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://vulnerability.circl.lu/rss/recent/osv_azurelinux/10</id>
  <title>Most recent entries from osv_azurelinux</title>
  <updated>2026-11-22T14:19:31.483136+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/azl-115916</id>
    <title>AZL-115916 — CVE-2026-133949 affecting package python-pip 24.2-12</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: python-pip</p>
<p>pip prior to v26.2.2 the certifi bundled with pip contains the compromised eMudhra certificates.</p>
<p>Upgrading to a secure version of pip should be done either by first upgrading Python to a version that rejects the compromised intermediates (CVE-2026-115557) or use hash pinning with a known-secure version of pip. pip is not vulnerable when using a Python version that rejects the compromised certificates. See the references below for more information.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115916"/>
    <published>2026-11-20T19:18:51+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/azl-115910</id>
    <title>AZL-115910 — CVE-2026-107493 affecting package shim-unsigned-x64 16.1-2</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: shim-unsigned-x64</p>
<p>Issue summary: When an application passes a stack to
PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,
OpenSSL frees every entry in the stack, both the old ones and any new
ones, but leaves them in the stack.</p>
<p>Impact summary: An application that passes an existing stack to
PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may
use memory that was already freed. This can cause a crash or, in
principle, memory corruption. Malformed PEM data can make the read fail,
but only applications that pass an existing stack are affected, and
OpenSSL itself does not do this.</p>
<p>CWE: CWE-416: Use After Free</p>
<p>Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and
private keys from PEM data and adds them to a stack of X509_INFO
structures. If the application passes a stack that is not NULL, the
function adds the new entries to it and must leave the entries that are
already there unchanged.</p>
<p>If reading fails, the function frees every entry in the stack. This
includes the entries that were there before the call, and the entries
added by the call. It does not remove these entries from the stack, so
the stack keeps pointers to freed memory. The failure can happen at any
point, even before any entry was added. A PEM item with invalid content
is enough.  This also happens if the stack was empty: entries added
before the failure are freed but stay in the stack.</p>
<p>An application that then reads or frees the stack will use memory that
was already freed. Thi…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115910"/>
    <published>2026-11-17T09:17:25+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/azl-115907</id>
    <title>AZL-115907 — CVE-2026-107493 affecting package shim-unsigned-aarch64 16.1-2</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: shim-unsigned-aarch64</p>
<p>Issue summary: When an application passes a stack to
PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,
OpenSSL frees every entry in the stack, both the old ones and any new
ones, but leaves them in the stack.</p>
<p>Impact summary: An application that passes an existing stack to
PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may
use memory that was already freed. This can cause a crash or, in
principle, memory corruption. Malformed PEM data can make the read fail,
but only applications that pass an existing stack are affected, and
OpenSSL itself does not do this.</p>
<p>CWE: CWE-416: Use After Free</p>
<p>Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and
private keys from PEM data and adds them to a stack of X509_INFO
structures. If the application passes a stack that is not NULL, the
function adds the new entries to it and must leave the entries that are
already there unchanged.</p>
<p>If reading fails, the function frees every entry in the stack. This
includes the entries that were there before the call, and the entries
added by the call. It does not remove these entries from the stack, so
the stack keeps pointers to freed memory. The failure can happen at any
point, even before any entry was added. A PEM item with invalid content
is enough.  This also happens if the stack was empty: entries added
before the failure are freed but stay in the stack.</p>
<p>An application that then reads or frees the stack will use memory that
was already freed. Thi…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115907"/>
    <published>2026-11-17T09:17:25+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/azl-115904</id>
    <title>AZL-115904 — CVE-2026-95690 affecting package rust 1.98.1-1</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: rust</p>
<p>Issue summary: Receiving crafted out-of-sequence DTLS handshake fragments may
cause OpenSSL to allocate a full message-length reassembly buffer for each
buffered message, so a small amount of wire data consumes a large amount of
memory.</p>
<p>Impact summary: A remote attacker can send a few small crafted DTLS handshake
fragments to make a DTLS server or client allocate well over a megabyte of
memory per connection, which may lead to memory exhaustion and Denial of
Service if many connections are made.</p>
<p>CWE: CWE-770: Allocation of Resources Without Limits or Throttling</p>
<p>Description: DTLS handshake messages can arrive out of order and fragmented,
so OpenSSL buffers fragments of up to ten out-of-sequence messages until
reassembly is possible. When the first fragment of a new message arrives,
OpenSSL allocates a buffer sized to the full message length declared in the
fragment header, plus a reassembly bitmap, instead of storing only the bytes
actually received. The declared length is capped by the maximum certificate
list size, 128KB by default, and that cap applies to every handshake message
type rather than only to Certificate messages.</p>
<p>Only DTLS endpoints reach this code. TLS, QUIC and applications that do not
use DTLS are unaffected. An attacker sends fragments that declare a large
message length but carry almost no data, using up to ten distinct message
sequence numbers.</p>
<p>A single connection can then hold roughly 1.4MB of buffers from about 156
bytes on the wire. Because the nu…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115904"/>
    <published>2026-11-18T12:17:24+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/azl-115901</id>
    <title>AZL-115901 — CVE-2026-124709 affecting package rust 1.98.1-1</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: rust</p>
<p>Issue summary: A QUIC server that rejects a stream opened by the peer may
retain that stream's state for the lifetime of the connection if the peer
resets the stream before the rejection is signalled, even though the peer's
stream credit is returned.</p>
<p>Impact summary: A remote client that completes a QUIC handshake can repeatedly
open and reset streams, causing server memory to grow without bound until the
process runs out of memory and every connection on it is lost. This is a
Denial of Service.</p>
<p>CWE: CWE-401: Missing Release of Memory after Effective Lifetime</p>
<p>Description: QUIC servers track each stream the peer opens. When the incoming
stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks
the stream deleted and returns the peer's stream credit. A deleted stream is
collected only once its receive part is fully drained, which for a rejected
stream means the STOP_SENDING has been acknowledged. If the peer sends
RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never
sent or acknowledged and the stream is never collected.</p>
<p>The default configuration reaches this path. Once a connection has a default
stream, meaning the application has read from or written to the connection as
the tutorial server does, the effective incoming stream policy rejects streams
the application does not accept. Applications that set the REJECT policy
explicitly are affected too.</p>
<p>Each retained stream costs about 300 bytes, and the peer's stream credit
windo…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115901"/>
    <published>2026-11-17T09:17:27+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/azl-115898</id>
    <title>AZL-115898 — CVE-2026-35190 affecting package rust 1.98.1-1</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: rust</p>
<p>Issue summary: A server configured with the Suite B certificate flag through
SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a
fixed group list when it processes a ClientHello whose supported_groups and
key_share contain no Suite B group.</p>
<p>Impact summary: A remote client can send a ClientHello that makes the server
read past the end of a static array. The values read are never returned to the
client, so no memory is disclosed; on builds with sanitizers or hardened
allocators the read may crash the process, causing Denial of Service.</p>
<p>CWE: CWE-125: Out-of-bounds Read</p>
<p>Description: When the Suite B certificate flag is set, OpenSSL restricts the
accepted groups to P-256 and P-384 by substituting a fixed two-element list
for the configured group list. The tuple machinery used for key-share
selection was not updated for this substitution: tls1_get_group_tuples() still
returns the configured tuples, which by default describe eight groups. The
server-side walk in tls_parse_ctos_key_share() then advances through the
two-element list using those tuple counts without checking the cumulative
offset against the number of groups present.</p>
<p>Only applications that call SSL_CTX_set_cert_flags() with
SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The
openssl s_server -suiteB_128 option sets an X.509 verification parameter
instead, so the stock command line server is not vulnerable. Default
configurations do not reach this code.</p>
<p>A client that o…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115898"/>
    <published>2026-11-17T09:17:27+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/azl-115895</id>
    <title>AZL-115895 — CVE-2026-107493 affecting package rust 1.98.1-1</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: rust</p>
<p>Issue summary: When an application passes a stack to
PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,
OpenSSL frees every entry in the stack, both the old ones and any new
ones, but leaves them in the stack.</p>
<p>Impact summary: An application that passes an existing stack to
PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may
use memory that was already freed. This can cause a crash or, in
principle, memory corruption. Malformed PEM data can make the read fail,
but only applications that pass an existing stack are affected, and
OpenSSL itself does not do this.</p>
<p>CWE: CWE-416: Use After Free</p>
<p>Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and
private keys from PEM data and adds them to a stack of X509_INFO
structures. If the application passes a stack that is not NULL, the
function adds the new entries to it and must leave the entries that are
already there unchanged.</p>
<p>If reading fails, the function frees every entry in the stack. This
includes the entries that were there before the call, and the entries
added by the call. It does not remove these entries from the stack, so
the stack keeps pointers to freed memory. The failure can happen at any
point, even before any entry was added. A PEM item with invalid content
is enough.  This also happens if the stack was empty: entries added
before the failure are freed but stay in the stack.</p>
<p>An application that then reads or frees the stack will use memory that
was already freed. Thi…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115895"/>
    <published>2026-11-17T09:17:25+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/azl-115892</id>
    <title>AZL-115892 — CVE-2026-84786 affecting package rust 1.98.1-1</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: rust</p>
<p>Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL
pointer when processing an unusual combination of certificate and TLSA
records.</p>
<p>Impact summary: The impact is limited to a client crash (potential Denial
of Service).</p>
<p>CWE: CWE-476: NULL Pointer Dereference</p>
<p>Description: A DANE-enabled TLS client that supports TLSA records with at
least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2)
usage may crash by dereferencing a NULL pointer if the server claims a trusted
CA's certificate to be its end-entity certificate and has an unusual mix of
associated TLSA records.</p>
<p>DANE SMTP clients should not be affected since only the
DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable
in SMTP.  For example, the Postfix MTA is not affected, while the Exim
MTA does not at present use OpenSSL's DANE implementation.</p>
<p>Use of DANE in validation of RFC7250 raw public keys (RPKs) is also
unaffected, as these only use DANE-EE(3) TLSA records.</p>
<p>Only applications that support combining the DANE PKI with a traditional PKI
are potentially affected.  A DANE-enabled browser or similar, that uses
OpenSSL's DANE API could be affected.</p>
<p>FIPS impact: no
The DANE API is outside the FIPS module boundary.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115892"/>
    <published>2026-11-18T12:17:23+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/azl-115889</id>
    <title>AZL-115889 — CVE-2026-124709 affecting package rust 1.75.0-31</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: rust</p>
<p>Issue summary: A QUIC server that rejects a stream opened by the peer may
retain that stream's state for the lifetime of the connection if the peer
resets the stream before the rejection is signalled, even though the peer's
stream credit is returned.</p>
<p>Impact summary: A remote client that completes a QUIC handshake can repeatedly
open and reset streams, causing server memory to grow without bound until the
process runs out of memory and every connection on it is lost. This is a
Denial of Service.</p>
<p>CWE: CWE-401: Missing Release of Memory after Effective Lifetime</p>
<p>Description: QUIC servers track each stream the peer opens. When the incoming
stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks
the stream deleted and returns the peer's stream credit. A deleted stream is
collected only once its receive part is fully drained, which for a rejected
stream means the STOP_SENDING has been acknowledged. If the peer sends
RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never
sent or acknowledged and the stream is never collected.</p>
<p>The default configuration reaches this path. Once a connection has a default
stream, meaning the application has read from or written to the connection as
the tutorial server does, the effective incoming stream policy rejects streams
the application does not accept. Applications that set the REJECT policy
explicitly are affected too.</p>
<p>Each retained stream costs about 300 bytes, and the peer's stream credit
windo…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115889"/>
    <published>2026-11-17T09:17:27+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/azl-115886</id>
    <title>AZL-115886 — CVE-2026-107493 affecting package rust 1.75.0-31</title>
    <updated>2026-11-21T05:31:45+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Azure Linux:3: rust</p>
<p>Issue summary: When an application passes a stack to
PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails,
OpenSSL frees every entry in the stack, both the old ones and any new
ones, but leaves them in the stack.</p>
<p>Impact summary: An application that passes an existing stack to
PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may
use memory that was already freed. This can cause a crash or, in
principle, memory corruption. Malformed PEM data can make the read fail,
but only applications that pass an existing stack are affected, and
OpenSSL itself does not do this.</p>
<p>CWE: CWE-416: Use After Free</p>
<p>Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and
private keys from PEM data and adds them to a stack of X509_INFO
structures. If the application passes a stack that is not NULL, the
function adds the new entries to it and must leave the entries that are
already there unchanged.</p>
<p>If reading fails, the function frees every entry in the stack. This
includes the entries that were there before the call, and the entries
added by the call. It does not remove these entries from the stack, so
the stack keeps pointers to freed memory. The failure can happen at any
point, even before any entry was added. A PEM item with invalid content
is enough.  This also happens if the stack was empty: entries added
before the failure are freed but stay in the stack.</p>
<p>An application that then reads or frees the stack will use memory that
was already freed. Thi…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/azl-115886"/>
    <published>2026-11-17T09:17:25+00:00</published>
  </entry>
</feed>
