https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 10:47:34 +0000 https://cve.radiocsirt.org/vuln/bdu:2026-09733 bdu:2026-09733 https://cve.radiocsirt.org/vuln/bdu:2026-09733 https://cve.radiocsirt.org/vuln/bell-cve-2026-14191 <p><strong>Affected:</strong> Alpaquita:23: unrar, Alpaquita:25: unrar, Alpaquita:stream: unrar</p> <p><strong>Affected:</strong> Alpaquita:23: unrar, Alpaquita:25: unrar, Alpaquita:stream: unrar</p> https://cve.radiocsirt.org/vuln/bell-cve-2026-14191 https://cve.radiocsirt.org/vuln/euvd-2026-335174 EUVD-2026-335174 https://cve.radiocsirt.org/vuln/euvd-2026-335174 https://cve.radiocsirt.org/vuln/fkie_cve-2026-14191 <p>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&#39;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&#39;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 &#39;unrar t x.part1.rev&#39;, WinRAR &#39;Repair archive&#39;, 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.</p> <p>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&#39;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&#39;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 &#39;unrar t x.part1.rev&#39;, WinRAR &#39;Repair archive&#39;, 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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-14191 https://cve.radiocsirt.org/vuln/ghsa-5hjj-fvq6-8j36 <p>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&#39;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&#39;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 &#39;unrar t x.part1.rev&#39;, WinRAR &#39;Repair archive&#39;, 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.</p> <p>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&#39;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&#39;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 &#39;unrar t x.part1.rev&#39;, WinRAR &#39;Repair archive&#39;, 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.</p> https://cve.radiocsirt.org/vuln/ghsa-5hjj-fvq6-8j36 https://cve.radiocsirt.org/vuln/msrc_cve-2026-14191 msrc_CVE-2026-14191 https://cve.radiocsirt.org/vuln/msrc_cve-2026-14191 https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-14191 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: unrar-nonfree, Ubuntu:18.04:LTS: unrar-nonfree, Ubuntu:20.04:LTS: unrar-nonfree, Ubuntu:22.04:LTS: unrar-nonfree, Ubuntu:24.04:LTS: unrar-nonfree, Ubuntu:25.10: unrar-nonfree, Ubuntu:26.04:LTS: unrar-nonfree</p> <p>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&#39;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&#39;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 &#39;unrar t x.part1.rev&#39;, WinRAR &#39;Repair archive&#39;, 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.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: unrar-nonfree, Ubuntu:18.04:LTS: unrar-nonfree, Ubuntu:20.04:LTS: unrar-nonfree, Ubuntu:22.04:LTS: unrar-nonfree, Ubuntu:24.04:LTS: unrar-nonfree, Ubuntu:25.10: unrar-nonfree, Ubuntu:26.04:LTS: unrar-nonfree</p> <p>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&#39;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&#39;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 &#39;unrar t x.part1.rev&#39;, WinRAR &#39;Repair archive&#39;, 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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-14191 https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2152 <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in win.rar WinRAR ausnutzen, um beliebigen Programmcode auszuführen.</p> <p>Ein entfernter, anonymer Angreifer kann eine Schwachstelle in win.rar WinRAR ausnutzen, um beliebigen Programmcode auszuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2152