CVE-2016-5746: libstorage, libstorage-ng, and yast-storage improperly store passphrases for encrypted storage devices in a te

Routine

MEDIUM 5.1MITIGATEMITIGATEMITIGATE

CVE-2016-5746 is a medium-severity flaw (CVSS 5.1) affecting libstorage, libstorage-ng, yast-storage. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

libstorage, libstorage-ng, and yast-storage improperly store passphrases for encrypted storage devices in a temporary file on disk, which might allow local users to obtain sensitive information by reading the file, as demonstrated by /tmp/libstorage-XXXXXX/pwdf.

Why this priority

No elevated risk signals yet

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	5.1 (Medium)
Attack vector	Local
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 57%)
CISA exploited list	No
Published	2016-09-26
Last modified	2026-06-17

Publisher (CNA): OpenText · Vendor: opensuse · yast

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

Am I affected?

Timeline

2016-09-26 15:59 UTCPublished CVE record published
2026-06-17 00:49 UTCUpdated Record last modified

opensuse libstorage MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libstorage || rpm -q libstorage || libstorage --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

opensuse libstorage-ng MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy libstorage-ng || rpm -q libstorage-ng || libstorage-ng --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

yast yast-storage MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy yast-storage || rpm -q yast-storage || yast-storage --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

opensuse leap MITIGATE

Affected: 42.1

Fixed in: no fixed release known

Safe to downgrade to: a release before 42.1

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

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-2016-5746?

libstorage: mitigate or apply the listed mitigation; libstorage-ng: mitigate or apply the listed mitigation; yast-storage: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-5746 being exploited?

CVE-2016-5746 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-2016-5746 affect?

CVE-2016-5746 affects libstorage, libstorage-ng, yast-storage. Severity is medium (CVSS 5.1). libstorage, libstorage-ng, and yast-storage improperly store passphrases for encrypted storage devices in a temporary file on disk, which might allow local users to obtain sensitive information by reading the file, as demonstrated by /tmp/l

How urgent is CVE-2016-5746?

Priority 29/100. No elevated risk signals yet.

References

← Back to latest CVEs