VYPR

Winrar

by Rarlab

CVEs (29)

  • CVE-2014-125119HigJul 25, 2025
    risk 0.61cvss epss 0.01

    A filename spoofing vulnerability exists in WinRAR when opening specially crafted ZIP archives. The issue arises due to inconsistencies between the Central Directory and Local File Header entries in ZIP files. When viewed in WinRAR, the file name from the Central Directory is…

  • CVE-2015-5663HigDec 30, 2015
    risk 0.48cvss 7.4epss 0.01

    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.

  • CVE-2019-25677MedApr 5, 2026
    risk 0.40cvss 6.2epss 0.00

    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…

  • CVE-2023-38831KEVAug 23, 2023
    risk 0.29cvss epss 0.98

    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…

  • CVE-2018-20250KEVFeb 5, 2019
    risk 0.28cvss epss 0.96

    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…

  • CVE-2025-8088KEVAug 8, 2025
    risk 0.13cvss epss 0.86

    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 …

  • CVE-2025-6218KEVJun 21, 2025
    risk 0.12cvss epss 0.86

    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…

  • CVE-2023-40477May 3, 2024
    risk 0.07cvss epss 0.13

    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…

  • CVE-2006-3845Jul 25, 2006
    risk 0.04cvss epss 0.08

    Stack-based buffer overflow in lzh.fmt in WinRAR 3.00 through 3.60 beta 6 allows remote attackers to execute arbitrary code via a long filename in a LHA archive.

  • CVE-2005-3262Oct 20, 2005
    risk 0.04cvss epss 0.09

    Format string vulnerability in RARLAB WinRAR 2.90 through 3.50 allows remote attackers to execute arbitrary code via format string specifiers in a UUE/XXE file, which are not properly handled when WinRAR displays diagnostic errors related to an invalid filename.

  • CVE-2004-1254Jan 10, 2005
    risk 0.04cvss epss 0.10

    WinRAR 3.40, and possibly earlier versions, allows remote attackers to execute arbitrary code via a ZIP file containing a file with a long filename, possibly causing an integer overflow that leads to a buffer overflow.

  • CVE-2006-3912Jul 28, 2006
    risk 0.03cvss epss 0.06

    Stack-based buffer overflow in the SFX module in WinRAR before 3.60 beta 8 has unspecified vectors and impact.

  • CVE-2005-4620Dec 31, 2005
    risk 0.03cvss epss 0.01

    Buffer overflow in WinRAR 3.50 and earlier allows local users to execute arbitrary code via a long command-line argument. NOTE: because this program executes with the privileges of the invoking user, and because remote programs do not normally have the ability to specify a…

  • CVE-2004-0234Aug 18, 2004
    risk 0.01cvss epss 0.10

    Multiple stack-based buffer overflows in the get_header function in header.c for LHA 1.14, as used in products such as Barracuda Spam Firewall, allow remote attackers or local users to execute arbitrary code via long directory or file names in an LHA archive, which triggers the…

  • CVE-2025-52331Nov 12, 2025
    risk 0.00cvss epss 0.00

    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…

  • CVE-2025-31334Apr 3, 2025
    risk 0.00cvss epss 0.01

    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…

  • CVE-2024-36052May 21, 2024
    risk 0.00cvss epss 0.01

    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.

  • CVE-2024-33899Apr 28, 2024
    risk 0.00cvss epss 0.01

    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.

  • CVE-2024-30370Apr 2, 2024
    risk 0.00cvss epss 0.01

    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…

  • CVE-2022-43650Mar 29, 2023
    risk 0.00cvss epss 0.23

    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…

Page 1 of 2