A TOCTOU (Time-of-Check-Time-of-Use) race condition vulnerability was found in the fixfiles script in policycoreutils. When running fixfiles relabel or fixfiles restore, the script used find and chcon commands to locate and relabel unlabeled files under /tmp and other directories. A local attacker could exploit a race window between the file discovery and the label change operation by swapping directory components with symlinks, causing chcon to follow the symlink and modify SELinux labels on arbitrary system files. This could undermine SELinux mandatory access control protections on critical files such as /etc/shadow.
CVE-2026-19079
Score 4.4 from GitHub Security Advisory published 2026-08-07. a secondary CVSS source baseline 4.4; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.4
- EG Score
- 4.4(high)
- EG Risk
- 20(Track)EG Risk 20/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 computedSeverity44% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 0%
- KEV
- Not listed
Published
August 7, 2026
Last Modified
August 14, 2026
Advisory Details (2)
Auto-updated Aug 7, 2026commit a556538c2d5d (SELinuxProject/selinux)
Fix landed in SELinuxProject/selinux commit a556538c2d5d — awaiting tagged release
https://github.com/SELinuxProject/selinux/commit/a556538c2d5d2583273e025b45c02651fef47679Vendor Advisories for CVE-2026-19079(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | policycoreutils-main-3.11-2.2.hum1 | 2026-08-07 | redhat |
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
(4 across 4 ecosystems)
Debian:11(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| policycoreutils | 3.1-3 ... 3.9-2 (15 versions) | — | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| policycoreutils | 3.10-1 ... 3.9-2 (13 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| policycoreutils | 3.10-1, 3.11-1, 3.8.1-2, 3.9-1, 3.9-2 | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| policycoreutils | 3.10-1, 3.11-1, 3.8.1-2, 3.9-1, 3.9-2 | — | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 22× in last 7d / 50× 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.
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 19:19 UTCVendor advisory
- 2026-08-20 19:19 UTCGHSA enrichment
- 2026-08-19 19:23 UTCVendor advisory
- 2026-08-19 19:23 UTCGHSA enrichment
- 2026-08-18 19:20 UTCVendor advisory
- 2026-08-18 19:20 UTCGHSA enrichment
- 2026-08-17 19:24 UTCEG score recompute
- 2026-08-17 19:24 UTCVendor advisory
- 2026-08-17 19:24 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 19:11 UTCEG score recompute
- 2026-08-16 19:11 UTCVendor advisory
- 2026-08-16 19:11 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 19:15 UTCEG score recompute
- 2026-08-15 19:15 UTCVendor advisory
- 2026-08-15 19:15 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 19:19 UTCVendor advisory
- 2026-08-14 19:19 UTCGHSA enrichment
- 2026-08-13 21:05 UTCVendor advisory
- 2026-08-13 21:05 UTCGHSA enrichment
- 2026-08-12 21:10 UTCVendor advisory
Show 25 moreShow fewer
- 2026-08-12 21:10 UTCGHSA enrichment
- 2026-08-11 21:14 UTCEG score recompute
- 2026-08-11 21:14 UTCVendor advisory
- 2026-08-11 21:14 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 00:00 UTCEPSS rescore
- 2026-08-10 21:19 UTCVendor advisory
- 2026-08-10 21:19 UTCGHSA enrichment
- 2026-08-09 21:23 UTCVendor advisory
- 2026-08-09 21:23 UTCGHSA enrichment
- 2026-08-08 21:28 UTCEG score recompute
- 2026-08-08 21:28 UTCVendor advisory
- 2026-08-08 21:28 UTCGHSA enrichment
- 2026-08-08 16:37 UTCEPSS rescore
- 2026-08-07 21:32 UTCEG score recompute
- 2026-08-07 21:32 UTCGHSA enrichment
- 2026-08-07 20:27 UTCEG score recompute
- 2026-08-07 20:27 UTCGHSA enrichment
- 2026-08-07 18:26 UTCEG score recompute
- 2026-08-07 18:26 UTCGHSA enrichment
- 2026-08-07 17:47 UTCEG score recompute
- 2026-08-07 17:47 UTCGHSA enrichment
- 2026-08-07 08:22 UTCEG score recompute
- 2026-08-07 07:33 UTCEG score recompute
- 2026-08-07 07:33 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-19079?
When was CVE-2026-19079 disclosed?
Is CVE-2026-19079 actively exploited?
What is the CVSS score of CVE-2026-19079?
How do I remediate CVE-2026-19079?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-19079
Is Your Infrastructure Affected by CVE-2026-19079?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.