Patch & vulnerability status
win.rar GmbH
WinRAR 7.23
Latest tracked version 7.23. Release status, tracked CVEs, and automated cross-platform patching for WinRAR.
Category: Compression
| Platform | Latest version | CVEs tracked | Last checked |
|---|---|---|---|
| Windows | 7.23 | 16 | 2026-08-10 |
Known vulnerabilities (CVEs) in WinRAR
Lavawall tracks 16 published CVEs affecting WinRAR, and deploys the versions that fix them automatically across your fleet.
| CVE | Published | Severity | Details | Vector |
|---|---|---|---|---|
| CVE-2025-8088 | 2025-08-08 12:15:29 | HIGH (9) | A path traversal vulnerability affecting the Windows version of WinRAR allows the attackers to execute arbitrary code by crafting malicious archive files. This vulnerability was exploited in the wild and was discovered by Anton Cherepanov, Peter Košinár, and Peter Strýček from ESET. | NETWORK |
| CVE-2025-6218 | 2025-06-21 01:15:29 | HIGH (8) | RARLAB WinRAR Directory Traversal Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of RARLAB WinRAR. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of file paths within archive files. A crafted file path can cause the process to traverse to unintended directories. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-27198. | NETWORK |
| CVE-2025-52331 | 2025-11-12 17:15:38 | MEDIUM (6) | Cross-site scripting (XSS) vulnerability in the generate report functionality in Rarlab WinRAR 7.11, allows attackers to disclose user information such as the computer username, generated report directory, and IP address. The generate report command includes archived file names without validation in the HTML report, which allows potentially malicious HTML tags to be injected into the report. User interaction is required. User must use the "generate report" functionality and open the report. | NETWORK |
| CVE-2025-31334 | 2025-04-03 06:15:43 | HIGH (8) | Issue that bypasses the "Mark of the Web" security warning function for files when opening a symbolic link that points to an executable file exists in WinRAR versions prior to 7.11. If a symbolic link specially crafted by an attacker is opened on the affected product, arbitrary code may be executed. | NETWORK |
| CVE-2024-36052 | 2024-05-21 17:15:09 | HIGH (8) | RARLAB WinRAR before 7.00, on Windows, allows attackers to spoof the screen output via ANSI escape sequences, a different issue than CVE-2024-33899. | NETWORK |
| CVE-2024-33899 | 2024-04-29 00:15:08 | HIGH (7) | RARLAB WinRAR before 7.00, on Linux and UNIX platforms, allows attackers to spoof the screen output, or cause a denial of service, via ANSI escape sequences. | NETWORK |
| CVE-2024-30370 | 2024-04-02 21:15:50 | HIGH (8) | RARLAB WinRAR Mark-Of-The-Web Bypass Vulnerability. This vulnerability allows remote attackers to bypass the Mark-Of-The-Web protection mechanism on affected installations of RARLAB WinRAR. User interaction is required to exploit this vulnerability in that the target must perform a specific action on a malicious page. The specific flaw exists within the archive extraction functionality. A crafted archive entry can cause the creation of an arbitrary file without the Mark-Of-The-Web. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current user. Was ZDI-CAN-23156. | LOCAL |
| CVE-2023-40477 | 2024-05-03 03:15:20 | HIGH (7) | RARLAB WinRAR Recovery Volume Improper Validation of Array Index Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of RARLAB WinRAR. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of recovery volumes. The issue results from the lack of proper validation of user-supplied data, which can result in a memory access past the end of an allocated buffer. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-21233. | NETWORK |
| CVE-2023-38831 | 2023-08-23 17:15:44 | HIGH (8) | RARLAB WinRAR before 6.23 allows attackers to execute arbitrary code when a user attempts to view a benign file within a ZIP archive. The issue occurs because a ZIP archive may include a benign file (such as an ordinary .JPG file) and also a folder that has the same name as the benign file, and the contents of the folder (which may include executable content) are processed during an attempt to access only the benign file. This was exploited in the wild in April through October 2023. | LOCAL |
| CVE-2022-43650 | 2023-03-29 19:15:22 | HIGH (7) | This vulnerability allows remote attackers to disclose sensitive information on affected installations of RARLAB WinRAR 6.11.0.0. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the parsing of ZIP files. Crafted data in a ZIP file can trigger a read past the end of an allocated buffer. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-19232. | LOCAL |
| CVE-2019-25677 | 2026-04-05 21:16:46 | MEDIUM (7) | WinRAR 5.61 contains a denial of service vulnerability that allows local attackers to crash the application by placing a malformed winrar.lng language file in the installation directory. Attackers can trigger the crash by opening an archive and pressing the test button, causing an access violation at memory address 004F1DB8 when the application attempts to read invalid data. | LOCAL |
| CVE-2018-20253 | 2019-02-13 01:29:00 | MEDIUM (7) | In WinRAR versions prior to and including 5.60, There is an out-of-bounds write vulnerability during parsing of a crafted LHA / LZH archive formats. Successful exploitation could lead to arbitrary code execution in the context of the current user. | NETWORK |
| CVE-2018-20252 | 2019-02-05 20:29:00 | MEDIUM (7) | In WinRAR versions prior to and including 5.60, there is an out-of-bounds write vulnerability during parsing of crafted ACE and RAR archive formats. Successful exploitation could lead to arbitrary code execution in the context of the current user. | NETWORK |
| CVE-2018-20251 | 2019-02-05 20:29:00 | MEDIUM (4) | In WinRAR versions prior to and including 5.61, there is path traversal vulnerability when crafting the filename field of the ACE format. The UNACE module (UNACEV2.dll) creates files and folders as written in the filename field even when WinRAR validator noticed the traversal attempt and requestd to abort the extraction process. the operation is cancelled only after the folders and files were created but prior to them being written, therefore allowing the attacker to create empty files and folders everywhere in the file system. | NETWORK |
| CVE-2018-20250 | 2019-02-05 20:29:00 | MEDIUM (8) | In WinRAR versions prior to and including 5.61, There is path traversal vulnerability when crafting the filename field of the ACE format (in UNACEV2.dll). When the filename field is manipulated with specific patterns, the destination (extraction) folder is ignored, thus treating the filename as an absolute path. | NETWORK |
| CVE-2015-5663 | 2015-12-30 05:59:00 | LOW (4) | The file-execution functionality in WinRAR before 5.30 beta 5 allows local users to gain privileges via a Trojan horse file with a name similar to an extensionless filename that was selected by the user. | LOCAL |
Why keeping WinRAR patched matters
Unpatched third-party applications are one of the most common ways attackers get in: 57% of breached MSP clients and 32% of ransomware cases trace back to a missing patch. Every WinRAR release that fixes a security bug is public, so attackers see it too, and an out-of-date install becomes a documented way in. Tracking the installed version on every machine and closing the gap quickly is what turns a disclosed CVE into a non-event.
How Lavawall® patches WinRAR
Lavawall® watches WinRAR releases and CVEs continuously, ranks each update by risk, and deploys it across your whole fleet, Windows, macOS, and Linux, from a single agent, independently of your RMM. You get one place to see which machines are behind on WinRAR, one policy to bring them current, and timestamped evidence for audits.
Frequently asked questions
What is the latest version of WinRAR?
Lavawall tracks WinRAR at version 7.23 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Lavawall tracks WinRAR at version 7.23 (last checked 2026-08-10). New releases are monitored continuously and can be deployed automatically across your fleet.
Does WinRAR have known security vulnerabilities (CVEs)?
Lavawall tracks 16 CVEs for WinRAR and remediates them automatically as part of patching.
Lavawall tracks 16 CVEs for WinRAR and remediates them automatically as part of patching.
How do I patch WinRAR automatically?
Deploy the Lavawall® agent and WinRAR updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Deploy the Lavawall® agent and WinRAR updates are applied automatically across Windows, macOS, and Linux, risk-ranked and reported, independently of your RMM.
Lavawall® monitors releases and CVEs for WinRAR through public information and proprietary statistical analysis, and can patch it automatically across your fleet.