CVE-2026-14191

Range taken from the CVE record, check it before committing. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>FIXME -- FIXME</topic>
    <affects>
      <package>
	<name>libunrar</name>
	<range><lt>7.23</lt></range>
      </package>
      <package>
	<name>unrar-iconv</name>
	<range><lt>7.23</lt></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<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'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.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-14191</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-14191</url>
    </references>
    <dates>
      <discovery>2026-07-01</discovery>
      <entry>2026-10-27</entry>
    </dates>
  </vuln>