CVE-2026-19079

SELinux label manipulation via fixfiles symlink race

Published Aug 7, 2026 · Updated Aug 7, 2026

A TOCTOU race in policycoreutils fixfiles on affected Red Hat platforms allows local users to alter labels on arbitrary system files. The script passes pathnames found under /tmp and related directories to chcon, which re-resolves them after discovery and follows attacker-swapped symlink components. Exploitation requires local access, winning the race, and an administrator concurrently running fixfiles relabel or fixfiles restore; successful exploitation undermines SELinux controls on critical files.

CVSS severity4.4
Medium
EPSS probability0.08%
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

A TOCTOU race in policycoreutils fixfiles on affected Red Hat platforms allows local users to alter labels on arbitrary system files. The script passes pathnames found under /tmp and related directories to chcon, which re-resolves them after discovery and follows attacker-swapped symlink components. Exploitation requires local access, winning the race, and an administrator concurrently running fixfiles relabel or fixfiles restore; successful exploitation undermines SELinux controls on critical files.

The record

CVE
CVE-2026-19079
Published
Aug 7, 2026
Updated
Aug 7, 2026
Vendor
389 Directory Server
Product
Red Hat Enterprise Linux 10
Classifications
CWE-367, T1222.002
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 7, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 7, 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 versions are unavailable in this record. Check the vendor advisory for version and patch details.

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

389 Directory Server · Red Hat Enterprise Linux 10Affected versions are unavailable in this record.
389 Directory Server · Red Hat Enterprise Linux 7Affected versions are unavailable in this record.
389 Directory Server · Red Hat Hardened ImagesAffected versions are unavailable in this record.
389 Directory Server · Red Hat Enterprise Linux 9Affected versions are unavailable in this record.
389 Directory Server · Red Hat OpenShift Container Platform 4Affected versions are unavailable in this record.
389 Directory Server · Red Hat Enterprise Linux 8Affected versions are unavailable in this record.

Published CVSS scores

4.4Red HatCVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N

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 exploitUnconfirmed

Weakness, pattern, technique

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
T1222.002Linux and Mac File and Directory Permissions Modification

Public exploit references

No public exploit references are available in this record.

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