← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2015-3246 exploited? Yes: in CISA KEV since 26 Aug 2026

Gociux · Red Hat Libuser · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2015-3246, Red Hat Libuser Race Condition Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 26 Aug 2026, 4033 days after it was published. It affects Red Hat Libuser. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 26 Aug 2026
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity7.4CVSS 3.1 · high
US federal due9 Sep 2026BOD 22-01 deadline

What it is

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.

VendorRed Hat (9 exploited CVEs in KEV)
ProductLibuser
VulnerabilityRed Hat Libuser Race Condition Vulnerability
Weaknessnot specified
Published11 Aug 2015
Added to KEV26 Aug 2026
Reported by (CNA)redhat

What to do

  1. Check whether you run it. Look for Libuser in your asset inventory, including appliances and cloud images. Stack check lists every exploited Red Hat CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 11 Aug 2015.
  4. Get told next time. Email alerts when CISA adds a CVE for Red Hat.

References

Questions

Is CVE-2015-3246 being exploited?

Yes. CISA added CVE-2015-3246 to the Known Exploited Vulnerabilities catalog on 26 Aug 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2015-3246 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

How do I fix CVE-2015-3246?

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. Check Red Hat's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected Libuser and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in August 2026 · Red Hat scorecard · act-now radar.

Running Red Hat in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →