VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

pulseaudio: vulnerability history, versions and safety

pulseaudio is a package in the Debian ecosystem. Vulert records 11 vulnerabilities for it across 21 releases, from Apr 2007 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
11 vulnerabilities recorded U11
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 01 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pulseaudio vulnerabilities

Vulert verdict on pulseaudio i

Updated on 23 Oct 2026

Careful: one of the 11 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 11 vulnerabilities on record across 19 years, 1 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 11 over 19 years · 1 in the last year i
  • Latest disclosure 01 Jul 2026 i
  • Highest CVSS 5.5 i
  • With no published fix 1 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for pulseaudio, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 21 of 21 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2007 2
  • 2008 2
  • 2009 2
  • 2010 2
  • 2014 2
  • 2026 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 11 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for pulseaudio

The 5 most severe of 11 vulnerabilities recorded for this package

Search all 11 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Memory Management Flaw in PulseAudio Package 5.5 medium No fix published 01 Jul 2026
Denial of Service Vulnerability in PulseAudio N/A unrated 0.9.6-1 02 Apr 2007
Privilege Escalation via Race Condition in PulseAudio N/A unrated 0.9.15-4.1 17 Jul 2009
Denial of Service in PulseAudio N/A unrated 5.0-3 11 Jun 2014
Privilege Escalation Vulnerability in PulseAudio: CVE-2008-0008 N/A unrated 0.9.9-1 29 Jan 2008

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About pulseaudio

Is pulseaudio safe to use?

Vulert records 11 vulnerabilities for pulseaudio in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does pulseaudio have?

11 vulnerabilities are recorded for pulseaudio in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 11 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pulseaudio vulnerabilities disclosed?

1 vulnerability was recorded for pulseaudio in the last 12 months, and the oldest entry in this database dates to 02 Apr 2007. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of pulseaudio are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor pulseaudio for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the pulseaudio version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.