{"id":1873,"date":"2026-07-20T10:15:24","date_gmt":"2026-07-20T10:15:24","guid":{"rendered":"https:\/\/thedigitalfortress.us\/?p=1873"},"modified":"2026-07-20T10:15:24","modified_gmt":"2026-07-20T10:15:24","slug":"new-7-zip-vulnerability-could-let-crafted-xz-archives-run-code-during-extraction","status":"publish","type":"post","link":"https:\/\/thedigitalfortress.us\/?p=1873","title":{"rendered":"New 7-Zip Vulnerability Could Let Crafted XZ Archives Run Code During Extraction"},"content":{"rendered":"
\n

\ue804<\/i>Swati Khandelwal<\/span>\ue802<\/i>Jul 20, 2026<\/span><\/span>Vulnerability \/ Endpoint Security<\/span><\/p>\n<\/div>\n

\n
<\/a><\/div>\n

Opening a crafted XZ archive in 7-Zip could let an attacker run code on the machine. The flaw, CVE-2026-14266<\/code>, is a heap-based buffer overflow in how the archiver processes XZ chunked data, and Trend Micro’s Zero Day Initiative (ZDI) detailed it<\/a> on July 15. A fix shipped on June 25 in 7-Zip 26.02<\/a>.<\/p>\n

The overflow lets an attacker \u00abexecute code in the context of the current process,\u00bb per the advisory. The code runs with the token 7-Zip itself holds and gains no privileges of its own.<\/p>\n

On Windows, a normally launched 7-Zip runs under a filtered standard-user token<\/a> even on an administrator account, so the attacker inherits those limited rights unless the program was started elevated. The bug came in from Landon Peng of Lunbun LLC, who reported it to 7-Zip on June 5.<\/p>\n

ZDI rates the flaw 7.0, or High, not the Critical several write-ups reached for. The full CVSS 3.0 vector is AV:L\/AC:H\/PR:N\/UI:R\/S:U\/C:H\/I:H\/A:H<\/code>. The AV:L<\/code> makes it a local attack vector, not a network-reachable or no-click one.<\/p>\n

ZDI’s \u00abremote code execution\u00bb describes a remote attacker delivering the file, which the victim still has to open, whether it arrives by email, a download, or a web page that hands it to 7-Zip. The high attack complexity makes reliable exploitation harder still. As of July 20, 2026, The Hacker News found no public proof-of-concept for the bug and no credible report of exploitation in the wild.<\/p>\n

\n
\"Cybersecurity\"<\/a><\/div>\n<\/div>\n

The Hacker News compared the XZ decoder source across releases. The fix lands in one function, MixCoder_Code<\/code> in C\/XzDec.c<\/code><\/a>. When an XZ stream runs its output through a filter, the decoder was handed the full output-buffer length on each pass instead of the space left after earlier writes. That gave it more room to work with than the buffer held, the out-of-bounds write condition ZDI describes.<\/p>\n

Version 26.02 subtracts the bytes already written and bails out if that running total ever exceeds the buffer. The same flawed length handling appears unchanged in 7-Zip source back to at least version 21.07 (2021), though neither ZDI nor 7-Zip has said which releases are actually exploitable.<\/p>\n

CVE-2026-14266 is the latest in a run of memory-safety bugs in 7-Zip’s archive handlers. On April 27, version 26.01 fixed a batch of them<\/a>, including the higher-scored CVE-2026-48095<\/a>, an NTFS-handler heap-write overflow that GitHub Security Lab detailed<\/a> on May 22 with a working proof-of-concept. The XZ flaw is the quieter of the two so far, and 26.02 rolls up every one of these fixes, so one update covers them all.<\/p>\n

So update to 7-Zip 26.02 or later on every machine that opens archives from outside. Updating is a manual install from the official site, so set-and-forget machines will not pick it up on their own. Any product that ships a vulnerable copy of 7-Zip’s XZ decoder needs its own vendor fix.<\/p>\n

The patch went out 20 days before the advisory, so anyone who updated in late June was covered before the details were public. For once, updating gets you ahead of the problem instead of chasing it.<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"

\ue804Swati Khandelwal\ue802Jul 20, 2026Vulnerability \/ Endpoint Security Opening a crafted XZ archive in 7-Zip could let an attacker run code on the machine. The flaw, CVE-2026-14266, is a heap-based buffer…<\/p>\n","protected":false},"author":1,"featured_media":1874,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[2432,2621,10,1684,2622,1774,68],"class_list":["post-1873","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-7zip","tag-archives","tag-code","tag-crafted","tag-extraction","tag-run","tag-vulnerability"],"_links":{"self":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/posts\/1873","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1873"}],"version-history":[{"count":0,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/posts\/1873\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=\/wp\/v2\/media\/1874"}],"wp:attachment":[{"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1873"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1873"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/thedigitalfortress.us\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1873"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}