<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://127.0.0.1:10001</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 21 Nov 2026 00:46:40 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-35469</title>
      <link>https://127.0.0.1:10001/vuln/bell-cve-2026-35469</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: containerd&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: containerd&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/bell-cve-2026-35469</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0456 — De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoqu…</title>
      <link>https://127.0.0.1:10001/vuln/certfr-2026-avi-0456</link>
      <description>certfr-2026-avi-0456</description>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/certfr-2026-avi-0456</guid>
    </item>
    <item>
      <title>Withdrawn: CLEANSTART-2026-AD69953 — Security fixes in argo-cd-fips 3.1.14-r0</title>
      <link>https://127.0.0.1:10001/vuln/cleanstart-2026-ad69953</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: argo-cd-fips&lt;/p&gt;
&lt;p&gt;Package argo-cd-fips version 3.1.14-r0 fixes 14 vulnerabilities: ghsa-mh2q-q3fh-2475, ghsa-p77j-4mvh-x3m3, ghsa-pc3f-x583-g7j2, ghsa-78h2-9frx-2jm8, ghsa-hfvc-g4fc-pqhx...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: argo-cd-fips&lt;/p&gt;
&lt;p&gt;Package argo-cd-fips version 3.1.14-r0 fixes 14 vulnerabilities: ghsa-mh2q-q3fh-2475, ghsa-p77j-4mvh-x3m3, ghsa-pc3f-x583-g7j2, ghsa-78h2-9frx-2jm8, ghsa-hfvc-g4fc-pqhx...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/cleanstart-2026-ad69953</guid>
    </item>
    <item>
      <title>OESA-2026-2162 — kubernetes security update</title>
      <link>https://127.0.0.1:10001/vuln/oesa-2026-2162</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kubernetes, openEuler:22.03-LTS-SP4: kubernetes, openEuler:24.03-LTS: kubernetes, openEuler:24.03-LTS-SP1: kubernetes, openEuler:24.03-LTS-SP3: kubernetes&lt;/p&gt;
&lt;p&gt;Container cluster management.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A flaw was found in the SPDY streaming code used by Kubelet, CRI-O, and kube-apiserver. An attacker with specific cluster roles, such as those allowing access to pod port forwarding, execution, or attachment, or node proxying, could exploit this vulnerability. This could lead to a Denial of Service (DoS) by causing the affected components to become unresponsive.(CVE-2026-35469)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.03-LTS-SP4: kubernetes, openEuler:22.03-LTS-SP4: kubernetes, openEuler:24.03-LTS: kubernetes, openEuler:24.03-LTS-SP1: kubernetes, openEuler:24.03-LTS-SP3: kubernetes&lt;/p&gt;
&lt;p&gt;Container cluster management.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A flaw was found in the SPDY streaming code used by Kubelet, CRI-O, and kube-apiserver. An attacker with specific cluster roles, such as those allowing access to pod port forwarding, execution, or attachment, or node proxying, could exploit this vulnerability. This could lead to a Denial of Service (DoS) by causing the affected components to become unresponsive.(CVE-2026-35469)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/oesa-2026-2162</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-35469</title>
      <link>https://127.0.0.1:10001/vuln/ubuntu-cve-2026-35469</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: golang-github-docker-spdystream, Ubuntu:18.04:LTS: golang-github-docker-spdystream, Ubuntu:20.04:LTS: golang-github-docker-spdystream, Ubuntu:22.04:LTS: golang-github-docker-spdystream, Ubuntu:24.04:LTS: golang-github-docker-spdystream, Ubuntu:25.10: golang-github-docker-spdystream, Ubuntu:26.10: golang-github-docker-spdystream, Ubuntu:26.04:LTS: golang-github-docker-spdystream&lt;/p&gt;
&lt;p&gt;spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: golang-github-docker-spdystream, Ubuntu:18.04:LTS: golang-github-docker-spdystream, Ubuntu:20.04:LTS: golang-github-docker-spdystream, Ubuntu:22.04:LTS: golang-github-docker-spdystream, Ubuntu:24.04:LTS: golang-github-docker-spdystream, Ubuntu:25.10: golang-github-docker-spdystream, Ubuntu:26.10: golang-github-docker-spdystream, Ubuntu:26.04:LTS: golang-github-docker-spdystream&lt;/p&gt;
&lt;p&gt;spdystream is a Go library for multiplexing streams over SPDY connections. In versions 0.5.0 and below, the SPDY/3 frame parser does not validate attacker-controlled counts and lengths before allocating memory. Three allocation paths are affected: the SETTINGS frame entry count, the header count in parseHeaderValueBlock, and individual header field sizes — all read as 32-bit integers and used directly as allocation sizes with no bounds checking. Because SPDY header blocks are zlib-compressed, a small on-the-wire payload can decompress into large attacker-controlled values. A remote peer that can send SPDY frames to a service using spdystream can exhaust process memory and cause an out-of-memory crash with a single crafted control frame. This issue has been fixed in version 0.5.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://127.0.0.1:10001/vuln/ubuntu-cve-2026-35469</guid>
    </item>
  </channel>
</rss>
