CVE-2026-73030

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. The CNA's CVSS baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-55802 (ENISA EUVD) · GHSA-2fcv-9f95-p67v (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.6%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

unearth through 0.18.2, fixed in commit 6c78164, contains a path traversal vulnerability in the is_within_directory function that fails to normalize paths before validation, allowing ../ sequences to bypass directory containment checks. Attackers can supply malicious tar archives with symlink members or traversal sequences to write files to arbitrary filesystem locations accessible to the process.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.
EPSS PROB
0.6%
EPSS %ILE
49th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-15). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (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 10, 2026

Last Modified

November 8, 2026

Advisory Details (4)

Auto-updated Aug 10, 2026
Patch available. Sources: github_pr, github_commit.
Web page

unearth 0.18.2 Path Traversal via Unnormalized Paths and Symlink Escape | Advisories | VulnCheck

https://www.vulncheck.com/advisories/unearth-path-traversal-via-unnormalized-paths-and-symlink-escape
GitHub commit

commit 6c78164e7bfa (frostming/unearth)

Fix landed in frostming/unearth commit 6c78164e7bfa — awaiting tagged release

https://github.com/frostming/unearth/commit/6c78164e7bfa28b8b3d6f247b87e560692e3c8ba
GitHub pull request

fix: prevent tar-slip via path traversal and symlink escape in _untar_archive

Fix merged in frostming/unearth PR #181 on 2026-08-05 — awaiting tagged release

https://github.com/frostming/unearth/pull/181
Web page

Tar-Slip in unearth sdist Extraction · Issue #180 · frostming/unearth · GitHub

https://github.com/frostming/unearth/issues/180

Vendor Advisories for CVE-2026-73030(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
unearth0.10.0+ds1-1 ... 0.9.2+ds1-1 (24 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
unearth0.17.5-1, 0.18.1-1, 0.18.2-1, 0.18.3-1, 0.18.3-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
unearth0.17.5-1, 0.18.1-1, 0.18.2-1
  • every version up to 0.18.3-1: fixed in 0.18.3-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 36× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 262 rows 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 162 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-73030?
CVE-2026-73030 is a high-severity vulnerability; its CVE record was published on August 10, 2026. unearth through 0.18.2, fixed in commit 6c78164, contains a path traversal vulnerability in the is_within_directory function that fails to normalize paths before validation, allowing ../ sequences to bypass directory containment checks. Attackers can supply malicious tar archives with symlink…
When was CVE-2026-73030 made public?
CVE-2026-73030 was made public on July 28, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 10, 2026. EchelonGraph's copy of the record carries a last-modified date of November 8, 2026; the record at its source may have been updated since.
Is CVE-2026-73030 actively exploited?
CVE-2026-73030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-73030?
CVE-2026-73030 has a CVSS base score of 8.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-73030?
A fix for CVE-2026-73030 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-73030 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-73030

Explore →

Is Your Infrastructure Affected by CVE-2026-73030?

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