Libuser vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited6 versions
The short answer

Libuser is made by Red Hat. We track 2 published vulnerabilities in it, across 6 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 26 August 2026. If you run Libuser, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Libuser flaw added to the known-exploited list is CVE-2015-3246, on 26 August 2026. We keep watching the known-exploited list.

Versions

Which versions of Libuser do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2015-3246Exploited list, 26 Aug 2026

    Red Hat Libuser Race Condition Vulnerability

    up to 0.56.13-50.60-10.60-20.60-30.60-40.60-50.60-6
Known exploited

Which Libuser vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.2
    CVE-2015-3246HighKnown exploited
    Red Hat Libuser Race Condition Vulnerability

    Red Hat libuser contains a race condition vulnerability that allows authenticated local users to corrupt the /etc/passwd file to cause a denial of service or privilege escalation.

    Chance of use8.5%Known exploited since26 Aug 2026
Exploit likelihood

Which Libuser flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 8.5%
    CVE-2015-3246HighKnown exploited

    libuser before 0.56.13-8 and 0.60 before 0.60-7, as used in the userhelper program in the usermode package, directly modifies /etc/passwd, which allows local users to cause a denial of service (inconsistent file...

    CVSS7.2Published11 Aug 2015
  2. 5.4%

    Incomplete blacklist vulnerability in the chfn function in libuser before 0.56.13-8 and 0.60 before 0.60-7, as used in the userhelper program in the usermode package, allows local users to cause a denial of service...

    CVSS2.1Published11 Aug 2015
EdgeProtect

Running Libuser? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 2 published vulnerabilities listed under the name Libuser, across 6 versions. The most recent Libuser flaw added to the known-exploited list is CVE-2015-3246, on 26 August 2026.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2015-3246.

Each flaw names its own versions, usually as ranges. The newest, CVE-2015-3246, affects up to 0.56.13-5, 0.60-1, 0.60-2, 0.60-3 and more. The versions for every exploited flaw are listed on this page.

Create a EdgeProtect account and track Libuser. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.