Home › Intelligence › Brief
VULNERABILITY BRIEF 🟠 High Vulnerability

Privilege Escalation in Red Hat ABRT (CVE-2015-5287) Risks Linux System Integrity

Red Hat’s Automatic Bug Reporting Tool (ABRT) contains a local privilege‑escalation flaw (CVE‑2015‑5287) that lets users with limited rights gain elevated privileges via a predictable‑name symlink attack. The issue affects supported and end‑of‑life RHEL releases, prompting immediate patching or migration. Organizations must address it to maintain audit‑ready evidence of vulnerability management.

Verisq™ Intelligence · 📅 October 07, 2026 · 📰 nvd.nist.gov
🟠
Severity
High
VU
Type
Vulnerability
🎯
Confidence
High
🏢
Affected
1 sector(s)
✅
Actions
3 recommended
📰
Source
nvd.nist.gov

Critical Privilege Escalation in Red Hat ABRT (CVE‑2015‑5287) Threatens Linux System Integrity

What It Is – Red Hat’s Automatic Bug Reporting Tool (ABRT) contains a local privilege‑escalation flaw (CVE‑2015‑5287). An attacker with limited permissions can craft a symlink to a predictable‑name file, causing ABRT to execute with elevated rights and granting the attacker higher privileges on the host.

Exploitability – The vulnerability is exploitable locally on any affected RHEL system; no public exploit code is required, and it can be triggered on both supported and end‑of‑life releases.

Affected Products – Red Hat Enterprise Linux (RHEL) installations that include ABRT, including versions that have reached end‑of‑life or end‑of‑service.

Why It Matters for Trust & Control Assurance

  • Demonstrates a gap in vulnerability‑management controls; continuous patching evidence is essential for audit readiness.
  • Remediation (patch or upgrade) must be recorded to provide defensible proof of due‑diligence to regulators and enterprise partners.
  • The issue highlights the need for control mapping across frameworks (e.g., NIST CSF 2.0) to show that patch‑management objectives are being met.

Recommended Actions

  1. Apply Red Hat’s security advisory patch for ABRT or upgrade to a supported RHEL version.
  2. Disable ABRT on systems where it is not required.
  3. Record remediation steps in your vulnerability‑management system and retain evidence for audit purposes.

Source: CISA KEV – CVE‑2015‑5287

📰 Original Source
https://nvd.nist.gov/vuln/detail/CVE-2015-5287 ↗

This Verisq Intelligence Brief is an independent analysis. Read the original reporting at the link above.

Vulnerability exposure

Is this CVE in your supply chain?

Verisq matches published vulnerabilities against the software your vendors run, so you know which relationships this touches before the next review.

See vendor exposure →