CVE-2026-4878

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
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%CVSS: 7.0Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in libcap. A local unprivileged user can exploit a Time-of-check-to-time-of-use (TOCTOU) race condition in the cap_set_file() function. This allows an attacker with write access to a parent directory to redirect file capability updates to an attacker-controlled file. By doing so, capabilities can be injected into or stripped from unintended executables, leading to privilege escalation.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
11%
KEV
Not listed

Published

April 9, 2026

Last Modified

July 27, 2026

Advisory Details (10)

Auto-updated Apr 30, 2026
Patch available. Sources: redhat.
generic

oss-security - Re: libcap-2.77 (since libcap-2.04) has TOCTOU privilege escalation issue

http://www.openwall.com/lists/oss-security/2026/04/09/5
generic

oss-security - Re: libcap-2.77 (since libcap-2.04) has TOCTOU privilege escalation issue

http://www.openwall.com/lists/oss-security/2026/04/08/9
generic

oss-security - libcap-2.77 (since libcap-2.04) has TOCTOU privilege escalation issue

http://www.openwall.com/lists/oss-security/2026/04/07/4
generic

oss-security - Re: libcap-2.77 (since libcap-2.04) has TOCTOU privilege escalation issue

http://www.openwall.com/lists/oss-security/2026/04/07/14
redhat Patch Available

2451615 – (CVE-2026-4878) CVE-2026-4878 libcap: libcap: Privilege escalation via TOCTOU race condition in cap_set_file()

Affected: Red Hat Enterprise Linux 10

https://bugzilla.redhat.com/show_bug.cgi?id=2451615
redhat

Bug Access Denied

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

cve-details

https://access.redhat.com/security/cve/CVE-2026-4878
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:7473
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:12441
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:12423

Vendor Advisories for CVE-2026-4878(20)

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

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17835391562026-07-15redhat
redhatrhcos-417.94.202606250942-02026-07-09redhat
redhatrhcos-414.92.202606231112-02026-07-01redhat
redhatrhcos-413.92.202606160406-02026-06-25redhat
redhatrhaiis/vllm-cuda-rhel9:17823528472026-06-25redhat
redhatrhaiis/vllm-rocm-rhel9:17823530932026-06-25redhat
redhatrhaiis/vllm-spyre-rhel9:17823529192026-06-25redhat
redhatrhaiis/model-opt-cuda-rhel9:17823529502026-06-25redhat
redhatdiscovery/discovery-ui-rhel9:17821669522026-06-24redhat
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17809462392026-06-22redhat
redhatrhcos-416.94.202606051757-02026-06-18redhat
redhatrhcos-418.94.202606051320-02026-06-17redhat
redhatrhcos-415.92.202606030318-02026-06-11redhat
redhatrhcos-4.19.9.6.202606031700-02026-06-10redhat
redhatrhaiis/model-opt-cuda-rhel9:17806819842026-06-10redhat
redhatlibcap-0:2.48-4.el8_6.12026-06-08redhat
redhatlibcap-0:2.48-5.el8_8.12026-06-03redhat
redhatinsights-proxy/insights-proxy-container-rhel9:17804204282026-06-02redhat
redhatlibcap-0:2.48-9.el9_2.12026-05-27redhat
redhatrhui5/rhua-rhel9:17797982222026-05-27redhat
redhatlibcap-0:2.48-9.el9_4.12026-05-26redhat
redhatlibcap-0:2.48-9.el9_6.12026-05-20redhat
redhatlibcap-0:2.69-7.el10_0.12026-05-20redhat
redhatlibcap-0:2.48-10.el9_8.12026-05-19redhat
redhatlibcap-0:2.69-7.el10_2.12026-05-19redhat
redhatdiscovery/discovery-ui-rhel9:17781567562026-05-07redhat
redhatrhosdt/opentelemetry-target-allocator-rhel9:17780562452026-05-06redhat
redhatlibcap-0:2.48-6.el8_10.12026-05-04redhat
redhatlibcap-0:2.69-7.el10_1.12026-04-30redhat
redhatlibcap-0:2.48-10.el9_7.12026-04-30redhat

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.

Additional Vendor Advisories

(11)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 15× in last 7d / 59× 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 127 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-4878?
CVE-2026-4878 is a high vulnerability published on April 9, 2026. A flaw was found in libcap. A local unprivileged user can exploit a Time-of-check-to-time-of-use (TOCTOU) race condition in the capsetfile() function. This allows an attacker with write access to a parent directory to redirect file capability updates to an attacker-controlled file. By doing so,…
When was CVE-2026-4878 disclosed?
CVE-2026-4878 was first published in the National Vulnerability Database on April 9, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4878 actively exploited?
CVE-2026-4878 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 89.2% of all scored CVEs.
What is the CVSS score of CVE-2026-4878?
CVE-2026-4878 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-4878?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4878, 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-4878

Explore →

Is Your Infrastructure Affected by CVE-2026-4878?

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

Start Free Scan →Browse All CVEs