Bandizip 7.47 is an archive manager for Windows and macOS that unpacks more than forty formats and compresses in about a dozen, leaning on multiple cores to cut the waiting. Between July and November it shipped four releases, and this one concentrates on security: three holes closed in a single pass, an uninstaller that could be used to gain privileges, the handling of the Mark of the Web, and the handling of symbolic links. Anyone who regularly downloads somebody else's archive and opens it has a reason to spend two minutes catching up.

An archive is a container. The moment it opens, its paths, links and file attributes land on your disk. The container does no harm by itself; what it carries does.

The first: privilege escalation in the uninstaller

This one carries the identifier KVE-2026-2462 and sits in the removal process. According to the vendor's changelog, the uninstall path contained a route by which arbitrary code could run with the rights of the owner. The danger in a privilege flaw is not what it can do but what it takes away: a program that should only touch its own directory suddenly holds the power to change system directories. The repair landed in 7.47, and the practical exposure depends on whether anything else on the machine can trigger that path.

The second: where the Mark of the Web goes

The Mark of the Web is a tag Windows attaches to files downloaded from a network, stored in an alternate data stream. With the tag present, Office opens a document in protected view, scripts are stopped, and an executable pulled down by a browser asks for one more confirmation. Archives are where this mechanism slips most easily: whether the extracted files inherit the mark of the container depends on the judgement of the extraction program. Version 7.47 repairs two problems in that judgement, filed as KVE-2026-2248 and KVE-2026-2099, with one of them reported by an outside researcher.

A wrong judgement means the mark is lost, and the files that come out are treated as local, so the prompt that should appear never does. The everyday weight of this is larger than it sounds. Plenty of people treat download, extract and double-click as one continuous motion, and the confirmation box in the middle is the only buffer. Remove the buffer and everything rests on the judgement made before extraction.

The third: how symbolic links are handled

The archive formats allow an entry inside to be a symbolic link. A correct extraction creates files inside the target directory, while the place a link points to may sit outside it. An extraction program that handles this badly follows the link and writes content to another path entirely, and what gets overwritten and where depends on who built the archive. The repair in 7.47 carries KVE-2026-2229, the third case of the same family.

Read together, the three share one logic

None of them is the compression algorithm computing wrongly. All three are a boundary that was not held. Extracting is by nature a write across a boundary, and permissions, marks and paths are each part of that boundary.

What Bandizip does the rest of the time

Setting the patch aside, the daily value lies in format coverage and in the number of steps. The extraction side lists more than forty formats, the common and the uncommon together: ZIP, RAR, 7Z, ALZ, EGG, WIM, XZ, ZPAQ. Compression covers ZIP, 7Z, ZIPX, self-extracting EXE, TAR, TGZ, LZH, ISO, GZ and XZ, and both split volumes and single files beyond four gigabytes are handled. Multiple cores are the point the vendor keeps pressing, with a quoted ceiling of six times the speed.

The smoothest part is the context menu and the smart extraction. Compressing and extracting happen from the file manager without opening the main window first; smart extraction looks at how many files the archive holds and decides whether a folder is needed, spreading a single file out and creating one level of directory for several, which spares the tidy-up afterwards. Encryption runs AES-256, with a password per archive. An ability that often goes unnoticed is editing inside an archive without extracting: deleting, renaming and adding all happen in the list, which is practical on an archive of several hundred megabytes.

Two checks it carries

After extraction an integrity test can be run, confirming that nothing was damaged on the way. Malicious code inside an archive is checked through the anti-malware scanning interface Microsoft provides, and the check happens at the listing stage before extraction, which means a warning can arrive before files reach the disk. Neither replaces an antivirus program, but both move the checkpoint to before opening.

The professional edition adds a few tools: a password manager that remembers the passwords of each archive, a repair function that analyses a broken ZIP and rescues what it can, password recovery by brute force, and an image preview that shows thumbnails of photos inside an archive without unpacking. The free edition already covers compression, extraction and the mainstream formats, and the vendor states in its FAQ that commercial use is allowed at no cost.

Whether to update right now

Anyone who only unpacks archives they made themselves faces little exposure and can update whenever convenient. If the workflow regularly brings archives from other people, or asset packs from forums and file hosts, this one belongs at the top of the list: all three holes sit on the act of opening an outside archive, and the attack surface runs along exactly that path.

Before updating, check the version number on the machine. 7.47 is where this round of repairs lands, and the vendor dates it 13 October 2026. Any installation below that number carries one layer less of protection when an archive of unknown origin is opened.