CVE-2016-1601: yast2-users before 3.1.47, as used in SUSE Linux Enterprise 12 SP1, does not properly set empty password field

This week

CRITICAL 9.8REMOTEWATCHLISTMITIGATE

CVE-2016-1601 is a critical-severity flaw (CVSS 9.8) affecting yast2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

yast2-users before 3.1.47, as used in SUSE Linux Enterprise 12 SP1, does not properly set empty password fields in /etc/shadow during an AutoYaST installation when the profile does not contain inst-sys users, which might allow attackers to have unspecified impact via unknown vectors.

Why this priority

Critical severity
Remotely exploitable, no login, no user action
On your watchlist

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

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.5% (top 16%)
CISA exploited list	No
Weakness	CWE-255
Published	2016-04-26
Last modified	2026-06-17

Publisher (CNA): OpenText · Vendor: suse

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

Am I affected?

Timeline

2016-04-26 14:59 UTCPublished CVE record published
2026-06-17 00:42 UTCUpdated Record last modified

suse yast2 MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

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-1601?

yast2: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-1601 being exploited?

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

CVE-2016-1601 affects yast2. Severity is critical (CVSS 9.8). yast2-users before 3.1.47, as used in SUSE Linux Enterprise 12 SP1, does not properly set empty password fields in /etc/shadow during an AutoYaST installation when the profile does not contain inst-sys users, which might allow attackers to

How urgent is CVE-2016-1601?

Priority 65/100. Critical severity; Remotely exploitable, no login, no user action; On your watchlist

Related CVEs

CVE-2011-3177 HIGH 7.8 MITIGATE The YaST2 network created files with world readable permissions which could have allowed local users to read s

References

← Back to latest CVEs