CVE-2026-54230

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

A symlink following vulnerability was found in the ABRT post-create event handler scripts in libreport. Event scripts write output files using shell redirections without the O_NOFOLLOW flag. If the target file is replaced with a symlink, the shell process running as root follows the symlink and writes content to the symlink target, allowing arbitrary file overwrites on the system.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

June 13, 2026

Last Modified

August 26, 2026

Advisory Details (2)

Auto-updated Jun 15, 2026
Patch available. Sources: redhat.
redhat

2488568 – (CVE-2026-54230) CVE-2026-54230 abrt: event handler scripts follow symlinks when writing output files, allowing arbitrary file overwrites

https://bugzilla.redhat.com/show_bug.cgi?id=2488568
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-54230

Vendor Advisories for CVE-2026-54230(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatabrt-0:2.10.9-26.el8_102026-08-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 53× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 278 total refreshes for this CVE.

  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-14 03:54 UTCEG score recompute
  3. 2026-09-14 03:54 UTCVendor advisory
  4. 2026-09-14 03:54 UTCGHSA enrichment
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-10 09:35 UTCEPSS rescore
  8. 2026-09-08 22:01 UTCEPSS rescore
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-04 05:06 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 04:40 UTCEPSS rescore
  15. 2026-08-30 23:32 UTCEG score recompute
  16. 2026-08-30 23:32 UTCVendor advisory
  17. 2026-08-30 23:32 UTCGHSA enrichment
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 20:42 UTCEG score recompute
  23. 2026-08-26 20:42 UTCVendor advisory
  24. 2026-08-26 20:42 UTCGHSA enrichment
  25. 2026-08-26 14:46 UTCEPSS rescore
Show 75 more
  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 23:42 UTCEG score recompute
  3. 2026-08-24 23:42 UTCVendor advisory
  4. 2026-08-24 23:42 UTCGHSA enrichment
  5. 2026-08-23 21:29 UTCVendor advisory
  6. 2026-08-23 21:29 UTCGHSA enrichment
  7. 2026-08-23 09:56 UTCEG score recompute
  8. 2026-08-23 09:56 UTCVendor advisory
  9. 2026-08-23 09:56 UTCGHSA enrichment
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 19:33 UTCVendor advisory
  13. 2026-08-21 19:33 UTCGHSA enrichment
  14. 2026-08-21 07:59 UTCEG score recompute
  15. 2026-08-21 07:59 UTCVendor advisory
  16. 2026-08-21 07:59 UTCGHSA enrichment
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 20:26 UTCVendor advisory
  19. 2026-08-20 20:26 UTCGHSA enrichment
  20. 2026-08-20 08:44 UTCEG score recompute
  21. 2026-08-20 08:44 UTCVendor advisory
  22. 2026-08-20 08:44 UTCGHSA enrichment
  23. 2026-08-19 17:04 UTCEPSS rescore
  24. 2026-08-19 13:33 UTCEG score recompute
  25. 2026-08-19 13:33 UTCVendor advisory
  26. 2026-08-19 13:33 UTCGHSA enrichment
  27. 2026-08-18 13:48 UTCEPSS rescore
  28. 2026-08-17 13:47 UTCEPSS rescore
  29. 2026-08-17 10:18 UTCVendor advisory
  30. 2026-08-17 10:18 UTCGHSA enrichment
  31. 2026-08-16 22:45 UTCEG score recompute
  32. 2026-08-16 22:45 UTCVendor advisory
  33. 2026-08-16 22:45 UTCGHSA enrichment
  34. 2026-08-16 14:56 UTCEPSS rescore
  35. 2026-08-16 11:06 UTCEG score recompute
  36. 2026-08-16 11:06 UTCVendor advisory
  37. 2026-08-16 11:06 UTCGHSA enrichment
  38. 2026-08-16 02:14 UTCEPSS rescore
  39. 2026-08-15 23:33 UTCVendor advisory
  40. 2026-08-15 23:33 UTCGHSA enrichment
  41. 2026-08-15 11:50 UTCEG score recompute
  42. 2026-08-15 11:50 UTCVendor advisory
  43. 2026-08-15 11:50 UTCGHSA enrichment
  44. 2026-08-15 01:30 UTCEPSS rescore
  45. 2026-08-15 00:15 UTCVendor advisory
  46. 2026-08-15 00:15 UTCGHSA enrichment
  47. 2026-08-14 12:42 UTCVendor advisory
  48. 2026-08-14 12:42 UTCGHSA enrichment
  49. 2026-08-14 01:09 UTCEG score recompute
  50. 2026-08-14 01:09 UTCVendor advisory
  51. 2026-08-14 01:09 UTCGHSA enrichment
  52. 2026-08-13 22:00 UTCEPSS rescore
  53. 2026-08-13 13:36 UTCVendor advisory
  54. 2026-08-13 13:36 UTCGHSA enrichment
  55. 2026-08-13 12:27 UTCVendor advisory
  56. 2026-08-13 12:27 UTCGHSA enrichment
  57. 2026-08-13 04:09 UTCGHSA enrichment
  58. 2026-08-12 16:36 UTCGHSA enrichment
  59. 2026-08-12 15:37 UTCEG score recompute
  60. 2026-08-12 15:37 UTCGHSA enrichment
  61. 2026-08-12 13:51 UTCEPSS rescore
  62. 2026-08-12 06:49 UTCGHSA enrichment
  63. 2026-08-11 18:49 UTCEG score recompute
  64. 2026-08-11 18:49 UTCGHSA enrichment
  65. 2026-08-11 07:16 UTCEG score recompute
  66. 2026-08-11 07:16 UTCGHSA enrichment
  67. 2026-08-11 00:00 UTCEPSS rescore
  68. 2026-08-10 19:43 UTCGHSA enrichment
  69. 2026-08-10 03:51 UTCGHSA enrichment
  70. 2026-08-09 16:18 UTCEG score recompute
  71. 2026-08-09 16:18 UTCGHSA enrichment
  72. 2026-08-09 13:46 UTCEPSS rescore
  73. 2026-08-09 04:45 UTCGHSA enrichment
  74. 2026-08-08 17:12 UTCEG score recompute
  75. 2026-08-08 17:12 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-54230?
CVE-2026-54230 is a high vulnerability published on June 13, 2026. A symlink following vulnerability was found in the ABRT post-create event handler scripts in libreport. Event scripts write output files using shell redirections without the O_NOFOLLOW flag. If the target file is replaced with a symlink, the shell process running as root follows the symlink and…
When was CVE-2026-54230 disclosed?
CVE-2026-54230 was first published in the National Vulnerability Database on June 13, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54230 actively exploited?
CVE-2026-54230 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54230?
CVE-2026-54230 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-54230?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54230, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54230

Explore →

Is Your Infrastructure Affected by CVE-2026-54230?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.