CVE-2026-23879

HIGHPre-NVD 8.08.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 55% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

py7zr is a Python-based library and utility to support 7zip archive compression, decompression, encryption and decryption. Versions 1.1.2 and below contain an an arbitrary file write vulnerability, which allows symbolic links to be recreated outside the destination directory via crafted malicious symbolic link chains. When using extractall to extract an archive, the library restores these symbolic links, linking them to arbitrary directories on the host file system. During extraction, the program only checks the link arcname within the destination directory, but ignores the combined symlink path resolution. Attackers can exploit this vulnerability by constructing malicious archives, thereby bypassing the directory boundary restrictions implemented by the extractor. Subsequent extraction of regular files through these symbolic links can result in arbitrary file writes. This vulnerability may lead to remote code execution, privilege escalation, data corruption, or denial of service. This issue has been fixed in version 1.1.3.

CVSS v3
8.0
EG Score
8.0HIGHmedium confidence
EG Risk
41
EG Risk 41/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
Severity80% × 45%
Exploitation1% × 40%
Automatability30% × 15%
EPSS PROB
0.6%
EPSS %ILE
45th
KEV
Not listed

Published

June 19, 2026

Last Modified

June 25, 2026

Advisory Details (2)

Auto-updated Jun 24, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github.
githubMentions a patch (unverified)🟡 PoC Available

Arbitrary File Write Vulnerability in py7zr · Advisory · miurahr/py7zr · GitHub

https://github.com/miurahr/py7zr/security/advisories/GHSA-q6rc-2cgv-63h7
github_release Patch Available

Release version 1.1.3: Fix multiple vulnerabilities

Patch available: miurahr/py7zr v1.1.3

https://github.com/miurahr/py7zr/releases/tag/v1.1.3

Vendor Advisories for CVE-2026-23879(1)

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

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
py7zr0.11.3+dfsg-1 ... 1.1.3+dfsg-1 (27 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
py7zr0.11.3+dfsg-5 ... 1.1.3+dfsg-4 (25 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
py7zr0.22.0+dfsg-1 ... 1.1.3+dfsg-4 (18 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
py7zr0.22.0+dfsg-1 ... 1.1.2+dfsg-1~exp1 (9 versions)
  • every version up to 1.1.2+dfsg-1: fixed in 1.1.2+dfsg-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
py7zr0.0.3 ... 1.1.2 (164 versions)
  • every version up to 1.1.3: fixed in 1.1.3
—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-23879?
CVE-2026-23879 is a high vulnerability published on June 19, 2026. py7zr is a Python-based library and utility to support 7zip archive compression, decompression, encryption and decryption. Versions 1.1.2 and below contain an an arbitrary file write vulnerability, which allows symbolic links to be recreated outside the destination directory via crafted malicious…
When was CVE-2026-23879 disclosed?
CVE-2026-23879 was first published on June 19, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23879 actively exploited?
CVE-2026-23879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23879?
CVE-2026-23879 has a CVSS base score of 8.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-23879?
A fix for CVE-2026-23879 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23879 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-23879

Explore →

Is Your Infrastructure Affected by CVE-2026-23879?

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

Book a Demo →Browse All CVEs