CVE-2026-27117

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.4% (30th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2026-8571 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

bit7z is a cross-platform C++ static library that allows the compression/extraction of archive files. Prior to version 4.0.11, a path traversal vulnerability ("Zip Slip") exists in bit7z's archive extraction functionality. The library does not adequately validate file paths contained in archive entries, allowing files to be written outside the intended extraction directory through three distinct mechanisms: relative path traversal, absolute path traversal, and symbolic link traversal. An attacker can exploit this by providing a malicious archive to any application that uses bit7z to extract untrusted archives. Successful exploitation results in arbitrary file write with the privileges of the process performing the extraction. This could lead to overwriting of application binaries, configuration files, or other sensitive data. The vulnerability does not directly enable reading of file contents; the confidentiality impact is limited to the calling application's own behavior after extraction. However, applications that subsequently serve or display extracted files may face secondary confidentiality risks from attacker-created symlinks. Fixes have been released in version 4.0.11. If upgrading is not immediately possible, users can mitigate the vulnerability by validating each entry's destination path before writing. Other mitigations include running extraction with least privilege and extracting untrusted archives in a sandboxed directory.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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.4%
EPSS %ILE
30th
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 (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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 every mission impact level.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 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). 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

February 24, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Path traversal vulnerability in bit7z · Advisory · rikyoz/bit7z · GitHub

https://github.com/rikyoz/bit7z/security/advisories/GHSA-qvjh-hhw4-3gx9
GitHub release Patch Available

Bit7z v4.0.11

Patch available: rikyoz/bit7z v4.0.11

https://github.com/rikyoz/bit7z/releases/tag/v4.0.11
GitHub commit

commit 9e020483eefa (rikyoz/bit7z)

Fix landed in rikyoz/bit7z commit 9e020483eefa — awaiting tagged release

https://github.com/rikyoz/bit7z/commit/9e020483eefa5825ec9310b1d869933d4f77f969
GitHub commit

commit 31763da9a3e4 (rikyoz/bit7z)

Fix landed in rikyoz/bit7z commit 31763da9a3e4 — awaiting tagged release

https://github.com/rikyoz/bit7z/commit/31763da9a3e41a199c141c8d71f6c11de24b45cf

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 40× 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 97 of 102 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 5 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-27117?
CVE-2026-27117 is a high-severity vulnerability; its CVE record was published on February 24, 2026. bit7z is a cross-platform C++ static library that allows the compression/extraction of archive files. Prior to version 4.0.11, a path traversal vulnerability ("Zip Slip") exists in bit7z's archive extraction functionality. The library does not adequately validate file paths contained in archive…
When was the CVE record for CVE-2026-27117 published?
The CVE record for CVE-2026-27117 was published on February 24, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-27117 actively exploited?
CVE-2026-27117 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27117?
CVE-2026-27117 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-27117?
A fix for CVE-2026-27117 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-27117

Explore →

Is Your Infrastructure Affected by CVE-2026-27117?

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

Book a Demo →Browse All CVEs