CVE-2026-19079

MEDIUMPre-NVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

Score 4.4 from GitHub Security Advisory published 2026-08-07. A secondary CVSS source baseline 4.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
20
EG Risk 20/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
Severity44% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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

August 7, 2026

Last Modified

September 1, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
Patch available. Sources: redhat, github_commit.
github_commit

commit a556538c2d5d (SELinuxProject/selinux)

Fix landed in SELinuxProject/selinux commit a556538c2d5d — awaiting tagged release

https://github.com/SELinuxProject/selinux/commit/a556538c2d5d2583273e025b45c02651fef47679
redhat

Bug Access Denied

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

Vendor 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 / EcosystemFix (by version range) / PatchReleasedSource
redhatpolicycoreutils-main-3.11-2.2.hum12026-08-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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
policycoreutils3.1-3 ... 3.9-2 (15 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
policycoreutils3.10-1 ... 3.9-2 (13 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
policycoreutils3.10-1, 3.11-1, 3.8.1-2, 3.9-1, 3.9-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
policycoreutils3.10-1, 3.11-1, 3.8.1-2, 3.9-1, 3.9-2
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 79× 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 182 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-19079?
CVE-2026-19079 is a medium vulnerability published on August 7, 2026. 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…
When was CVE-2026-19079 disclosed?
CVE-2026-19079 was first published on August 7, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19079 actively exploited?
CVE-2026-19079 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-19079?
CVE-2026-19079 has a CVSS base score of 4.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-19079?
A fix for CVE-2026-19079 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-19079 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-19079

Explore →

Is Your Infrastructure Affected by CVE-2026-19079?

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

Book a Demo →Browse All CVEs