Approved changes feed: RSS · Atom
cpe:2.3:a:rarlab:winrar:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Rarlab (8c25d7e7-d80a-5deb-91c5-65b39ac8ced7) |
|---|---|
| Product | Winrar (0f8f275e-0e05-5261-a96c-4c3ef1433229) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-14191 |
vulnerable | 2026-07-29 00:26:16.860358 |
WinRAR / UnRAR RAR5 recovery-volume (.rev) out-of-bounds heap write in RecVolumes5::ReadHeader
HIGH (7.8)
An out-of-bounds heap write exists in the RAR5 recovery-volume (.rev) parser in WinRAR and UnRAR (RecVolumes5::ReadHeader in recvol5.cpp). The RecItems vector is sized only when the first .rev file in a set is processed; subsequent .rev files supply an independent RecNum value that is validated against that file's own TotalCount field but never against the actual size of RecItems. A crafted set of two or more .rev files can therefore write an attacker-controlled 32-bit value (the header's RevCRC field) to RecItems[RecNum] at an attacker-controlled offset up to 65534 * sizeof(RecVolItem) bytes past the allocation, corrupting adjacent heap objects. Triggering requires the victim to run a recovery/test operation on an attacker-supplied .rev set (for example 'unrar t x.part1.rev', WinRAR 'Repair archive', or auto-recovery when extracting a volume set with a missing .rar part). This is the RAR5-path sibling of CVE-2023-40477 (which was fixed in the RAR3 path only in WinRAR 6.23). Fixed in WinRAR / RAR 7.23.
Published: 2026-07-01T02:41:39.316Z
Updated: 2026-07-09T04:47:54.319Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-8088 |
vulnerable | 2026-06-08 07:45:19.415626 |
Path traversal vulnerability in WinRAR
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.
Published: 2025-08-08T11:11:41.842Z
Updated: 2026-08-11T03:55:29.502Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-6218 |
vulnerable | 2026-06-08 07:43:14.562120 |
RARLAB WinRAR Directory Traversal Remote Code Execution Vulnerability
HIGH (7.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.
Published: 2025-06-21T00:09:02.884Z
Updated: 2026-02-26T17:50:27.554Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-31334 |
vulnerable | 2026-06-08 07:17:02.757637 |
Details available
MEDIUM (6.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.
Published: 2025-04-03T05:27:32.538Z
Updated: 2025-04-03T13:52:45.659Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-36052 |
vulnerable | 2026-06-08 06:39:43.562094 |
Details available
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.
Published: 2024-05-21T16:37:49.665Z
Updated: 2025-02-13T15:59:12.307Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-33899 |
vulnerable | 2026-06-08 06:37:32.275511 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-30370 |
vulnerable | 2026-06-08 06:35:29.657455 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-40477 |
vulnerable | 2026-06-08 06:11:03.311598 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-38831 |
vulnerable | 2026-06-08 06:08:18.872565 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-43650 |
vulnerable | 2026-06-08 05:49:33.673511 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-20253 |
vulnerable | 2026-06-08 05:11:26.905648 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-20252 |
vulnerable | 2026-06-08 05:11:26.905135 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-20251 |
vulnerable | 2026-06-08 05:11:26.904683 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2018-20250 |
vulnerable | 2026-06-08 05:11:26.904230 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2014-125119 |
vulnerable | 2026-06-08 05:05:15.872011 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2008-7144 |
vulnerable | 2026-06-08 04:51:05.687988 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.