CVE-2026-79655

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A flaw was found in sos clean, a utility within the sos package. This vulnerability allows a local attacker to perform arbitrary file creation or overwrite. By crafting a malicious tar archive, an attacker can exploit a path traversal issue during tar extraction, where symlink and hardlink targets are not properly validated. This enables the attacker to write files to arbitrary locations on the system with the privileges of the sos clean process, which often runs as root.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
51
EG Risk 51/100

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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 25, 2026

Last Modified

October 6, 2026

Advisory Details (4)

Auto-updated Aug 25, 2026
Patch available. Sources: github_pr, redhat.
Web page

[cleaner] extract follows out-of-tree tar symlinks · Issue #4460 · sosreport/sos · GitHub

https://github.com/sosreport/sos/issues/4460
GitHub pull request

[cleaner] refuse out-of-tree tar members on extract

Upstream fix in progress (PR #4461 · sosreport/sos, state=open)

https://github.com/sosreport/sos/pull/4461
Red Hat

2523363 – (CVE-2026-79655) CVE-2026-79655 sos: sos: path traversal in sos clean tar extraction via unvalidated symlink/hardlink targets leads to arbitrary file write

https://bugzilla.redhat.com/show_bug.cgi?id=2523363
Red HatMentions a patch (unverified)

CVE-2026-79655 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-79655

Vendor Advisories for CVE-2026-79655(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
sos4.10.0-1 ... 4.9.2-3 (23 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
sos4.10.0-1 ... 4.9.2-3 (22 versions)
  • every version up to 4.12.0-2: fixed in 4.12.0-2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 153× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 240 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 140 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-79655?
CVE-2026-79655 is a high-severity vulnerability; its CVE record was published on August 25, 2026. A flaw was found in sos clean, a utility within the sos package. This vulnerability allows a local attacker to perform arbitrary file creation or overwrite. By crafting a malicious tar archive, an attacker can exploit a path traversal issue during tar extraction, where symlink and hardlink targets…
When was CVE-2026-79655 made public?
CVE-2026-79655 was made public on August 21, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 25, 2026. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-79655 actively exploited?
CVE-2026-79655 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-79655?
CVE-2026-79655 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-79655?
A fix for CVE-2026-79655 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-79655 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-79655

Explore →

Is Your Infrastructure Affected by CVE-2026-79655?

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

Book a Demo →Browse All CVEs