CVE-2026-4878Public exploit

Privilege escalation via cap_set_file path race

Published Apr 9, 2026 · Updated Aug 25, 2026

Privilege escalation in libcap before 2.78 allows local users to alter file capabilities on unintended executables via a path race. In cap_set_file() in cap_file.c, libcap checks the pathname with lstat() but later calls setxattr() or removexattr() on the same path, so a writable parent directory lets an attacker swap in a symlink or different file with renameat2(RENAME_EXCHANGE) between check and use. Exploitation requires local access and write permission in the target file's parent directory while a privileged caller such as setcap or container tooling updates capabilities on an attacker-influenced path, enabling capability injection into an attacker-controlled executable or capability stripping from another file.

CVSS severity6.7
Medium
EPSS probability0.21%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Privilege escalation in libcap before 2.78 allows local users to alter file capabilities on unintended executables via a path race. In cap_set_file() in cap_file.c, libcap checks the pathname with lstat() but later calls setxattr() or removexattr() on the same path, so a writable parent directory lets an attacker swap in a symlink or different file with renameat2(RENAME_EXCHANGE) between check and use. Exploitation requires local access and write permission in the target file's parent directory while a privileged caller such as setcap or container tooling updates capabilities on an attacker-influenced path, enabling capability injection into an attacker-controlled executable or capability stripping from another file.

The record

CVE
CVE-2026-4878
Published
Apr 9, 2026
Updated
Aug 25, 2026
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-367, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Apr 9, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

7.0NVDCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
6.7cve.orgCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H
6.7Red HatCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
T1068Exploitation for Privilege Escalation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo