CVE-2016-1585: In all versions of AppArmor mount rules are accidentally widened when compiled.

This month

CRITICAL 9.8REMOTEUPGRADE

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

In all versions of AppArmor mount rules are accidentally widened when compiled.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 36%)
CISA exploited list	No
Published	2019-04-22
Last modified	2026-06-17

Publisher (CNA): Canonical Ltd. · Vendor: canonical

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

Am I affected?

Timeline

2019-04-22 16:29 UTCPublished CVE record published
2026-06-17 00:42 UTCUpdated Record last modified

canonical apparmor UPGRADE

Affected: < 2.13.10 · >= 3.0.0 and < 3.0.12 · >= 3.1.0 and < 3.1.6

Fixed in: 2.13.10, 3.0.12, 3.1.6

Safe to downgrade to: a release before 3.0.0

1. Check installed version

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

2. UPGRADE to 2.13.10 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade apparmor

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade apparmor

Note

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

3. If no update is available yet, DOWNGRADE to a release before 3.0.0 (Debian / Ubuntu)

apt-cache madison apparmor sudo apt install apparmor=<VERSION_BEFORE_3.0.0> sudo apt-mark hold apparmor

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list apparmor sudo dnf downgrade apparmor-<VERSION_BEFORE_3.0.0> sudo dnf versionlock add apparmor

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

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

apparmor: upgrade to 2.13.10, 3.0.12, 3.1.6. Exact commands for each OS are on this page.

Is CVE-2016-1585 being exploited?

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

CVE-2016-1585 affects apparmor. Severity is critical (CVSS 9.8). In all versions of AppArmor mount rules are accidentally widened when compiled.

How urgent is CVE-2016-1585?

Priority 55/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2017-6507 MEDIUM 5.9 UPGRADE MITIGATE An issue was discovered in AppArmor before 2.12
CVE-2014-1424 MEDIUM 6.4 UPGRADE MITIGATE apparmor_parser in the apparmor package before 2.8.95~2430-0ubuntu5.1 in Ubuntu 14.04 allows attackers to bypa

References

← Back to latest CVEs