Skip to content

CVE-2015-3246

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…

Not rated yet Known exploited
Severity
Not rated yet
No source has published a CVSS score yet
Exploit chance (EPSS)
8.50%
Chance of exploitation in the next 30 days. Higher than 95.04% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Aug 26, 2026
Weakness
—
Not classified
Fix
None yet
No fixed version published
Exploited in the wild. Red Hat Libuser Race Condition Vulnerability (Red Hat Libuser). Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Due for U.S. federal agencies by Sep 9, 2026.

Description

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 state) by causing an error during the modification. NOTE: this issue can be combined with CVE-2015-3245 to gain privileges.

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Added to CISA's Known Exploited Vulnerabilities catalog
  4. Remediation due for U.S. federal agencies
  5. Latest EPSS score
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor