<?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/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T18:57:31.453372+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/cve-2020-16123</id>
    <title>CVE-2020-16123 — Bypass of snapd pulseaudio restrictions</title>
    <updated>2026-09-29T18:57:31.455704+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Canonical pulseaudio</p>
<p>An Ubuntu-specific patch in PulseAudio created a race condition where the snap policy module would fail to identify a client connection from a snap as coming from a snap if SCM_CREDENTIALS were missing, allowing the snap to connect to PulseAudio without proper confinement. This could be exploited by an attacker to expose sensitive information. Fixed in 1:13.99.3-1ubuntu2, 1:13.99.2-1ubuntu2.1, 1:13.99.1-1ubuntu3.8, 1:11.1-1ubuntu7.11, and 1:8.0-0ubuntu3.15.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2020-16123"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-4640-1</id>
    <title>USN-4640-1 — pulseaudio vulnerability</title>
    <updated>2026-09-29T18:57:31.455823+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:16.04:LTS: pulseaudio, Ubuntu:18.04:LTS: pulseaudio, Ubuntu:20.04:LTS: pulseaudio</p>
<p>James Henstridge discovered that an Ubuntu-specific patch caused
PulseAudio to incorrectly handle snap client connections. An attacker
could possibly use this to expose sensitive information.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-4640-1"/>
  </entry>
</feed>
