CVE-2018-25028: An issue was discovered in the libpulse-binding crate before 1.2.1 for Rust

Q: How do I fix CVE-2018-25028?

libpulse-binding: upgrade to 1.2.1. Exact commands for each OS are on this page.

Q: Is CVE-2018-25028 being exploited?

CVE-2018-25028 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2018-25028 affect?

CVE-2018-25028 affects libpulse-binding. Severity is high (CVSS 7.5). An issue was discovered in the libpulse-binding crate before 1.2.1 for Rust. get_context can cause a use-after-free.

Q: How urgent is CVE-2018-25028?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

This month

HIGH 7.5REMOTEUPGRADE

CVE-2018-25028 is a high-severity flaw (CVSS 7.5) affecting libpulse-binding. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in the libpulse-binding crate before 1.2.1 for Rust. get_context can cause a use-after-free.

Why this priority

High severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-416
Published	2021-12-27
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: libpulse-binding project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-12-27 00:15 UTCPublished CVE record published
2026-06-17 01:54 UTCUpdated Record last modified

libpulse-binding project libpulse-binding UPGRADE

Affected: < 1.2.1

Fixed in: 1.2.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libpulse-binding || rpm -q libpulse-binding || libpulse-binding --version

2. UPGRADE to 1.2.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libpulse-binding

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libpulse-binding

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-25028?

libpulse-binding: upgrade to 1.2.1. Exact commands for each OS are on this page.

Is CVE-2018-25028 being exploited?

CVE-2018-25028 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-25028 affect?

CVE-2018-25028 affects libpulse-binding. Severity is high (CVSS 7.5). An issue was discovered in the libpulse-binding crate before 1.2.1 for Rust. get_context can cause a use-after-free.

How urgent is CVE-2018-25028?

Priority 48/100. High severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2019-25055 HIGH 7.5 UPGRADE An issue was discovered in the libpulse-binding crate before 2.6.0 for Rust
CVE-2018-25027 HIGH 7.5 UPGRADE An issue was discovered in the libpulse-binding crate before 1.2.1 for Rust
CVE-2018-25001 MEDIUM 6.5 UPGRADE An issue was discovered in the libpulse-binding crate before 2.5.0 for Rust

References

← Back to latest CVEs