CVE-2026-54229

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-06-13. a secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A race condition was found in the abrt-dbus D-Bus service's ChownProblemDir method. ChownProblemDir opens the dump directory with DD_OPEN_READONLY and calls dd_chown to change ownership of all files to the caller's uid, succeeding even while post-create event handlers hold a write lock. This allows an attacker to gain filesystem-level control of the dump directory while privileged event scripts are still running.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

Published

June 13, 2026

Last Modified

August 13, 2026

Advisory Details (2)

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

2488532 – (CVE-2026-54229) CVE-2026-54229 abrt: ChownProblemDir succeeds during active post-create event processing due to inadequate locking

https://bugzilla.redhat.com/show_bug.cgi?id=2488532
redhatMentions a patch (unverified)

cve-details

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

Vendor Advisories for CVE-2026-54229(6)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatabrt-0:2.10.9-26.el8_102026-08-12redhat
redhatabrt-0:2.10.9-25.el8_8.12026-07-31redhat
redhatabrt-0:2.1.11-61.el7_92026-07-31redhat
redhatabrt-0:2.10.9-25.el8_4.12026-07-31redhat
redhatabrt-0:2.10.9-25.el8_6.12026-07-31redhat

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 / 26× 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 289 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Same vendor

3 shown

redhat:RHSA-2026:48819 · redhat:RHSA-2026:54272

Frequently asked(5)

What is CVE-2026-54229?
CVE-2026-54229 is a high vulnerability published on June 13, 2026. A race condition was found in the abrt-dbus D-Bus service's ChownProblemDir method. ChownProblemDir opens the dump directory with DDOPENREADONLY and calls dd_chown to change ownership of all files to the caller's uid, succeeding even while post-create event handlers hold a write lock. This allows…
When was CVE-2026-54229 disclosed?
CVE-2026-54229 was first published on June 13, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54229 actively exploited?
CVE-2026-54229 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54229?
CVE-2026-54229 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54229?
A fix for CVE-2026-54229 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54229 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54229?

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

Book a Demo →Browse All CVEs