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.1% (3rd percentile of EPSS-scored CVEs). 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.1%CVSS: 7.0Exploit: None knownExposed services: Not assessed

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.0HIGHmedium confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 9, 2026

Last Modified

October 9, 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
redhatMentions a patch (unverified)

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
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-4878
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:7473
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:12441
redhatMentions a patch (unverified)

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 / EcosystemFix (by version range) / PatchReleasedSource
redhatrhai/base-image-neuron-rhel9:17907035422026-10-01redhat
redhatcert-manager/cert-manager-trust-manager-rhel9:17905985932026-09-28redhat
redhatrhcos-412.86.202608241157-02026-09-03redhat
redhatrhui5/rhua-tp-rhel9:17872412602026-08-24redhat
redhatcostmanagement/costmanagement-metrics-rhel9-operator:17835391562026-07-15redhat
redhatrhcos-417.94.202606250942-02026-07-09redhat
redhatrhcos-414.92.202606231112-02026-07-01redhat
redhatrhaiis/vllm-rocm-rhel9:17823530932026-06-25redhat
redhatrhaiis/vllm-cuda-rhel9:17823528472026-06-25redhat
redhatrhcos-413.92.202606160406-02026-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.69-7.el10_0.12026-05-20redhat
redhatlibcap-0:2.48-9.el9_6.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

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.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
libcap—
  • every version up to 2.78-r0: fixed in 2.78-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
libcap—
  • every version up to 2.78-r0: fixed in 2.78-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
libcap—
  • every version up to 2.78-r0: fixed in 2.78-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
libcap—
  • every version up to 2.78-r0: fixed in 2.78-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
libcap—
  • every version up to 2.78-r0: fixed in 2.78-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
libcap21:2.44-1 ... 1:2.78-1 (30 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libcap21:2.66-4, 1:2.66-4+deb12u1, 1:2.66-4+deb12u2
  • every version up to 1:2.66-4+deb12u3: fixed in 1:2.66-4+deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libcap21:2.75-10
  • every version up to 1:2.75-10+deb13u1: fixed in 1:2.75-10+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libcap21:2.75-10, 1:2.77-1
  • every version up to 1:2.78-1: fixed in 1:2.78-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

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 10× in last 7d / 28× 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 314 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 on April 9, 2026, with the most recent update on October 9, 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.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-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?
A fix for CVE-2026-4878 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4878 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs