CVE and update status of the FreeBSD ports tree3,789 unaddressed CVEs in 711 portsAll times are CET
CVE details

CVE-2026-125264

FFmpeg through 9.0.2 contains an uncontrolled resource consumption vulnerability in parse_frame_header() in libavcodec/jpegxl_parser.c that fails to validate TOC entry counts against remaining input. Attackers can supply a crafted JPEG XL frame header with a permuted TOC and huge toc_count, making the parser loop excessively and exhaust CPU.

Score
6.8 medium
Published
2026-11-09
Links
NVD · cve.org · Report wrong data

Matched ports (5)

PortPackageVersionStatusMaintainer
multimedia/ffmpegffmpeg9.0.2_3,1unaddressedmultimedia@FreeBSD.org
multimedia/ffmpegffmpeg-nox119.0.2_3,1unaddressedmultimedia@FreeBSD.org
multimedia/ffmpeg3ffmpeg33.0.2_1unaddressedkreinholz@gmail.com
multimedia/ffmpeg4ffmpeg44.4.8_2unaddressedmonwarez@mailoo.org
multimedia/linux-rl9-ffmpeglinux-rl9-ffmpeg-libs7.1.5possibly backportedemulation@FreeBSD.org

Template for a VuXML entry

Check the content

Check the version numbers before you commit this entry. Some ports share an entry in the CVE database with another port, such as sqlite2 and sqlite3. The version shown here may then be one that never existed for this port.

Ranges per package from the CVE rows that match this port, in pkg notation with the port's epoch and revision, every bound checked with pkg; one range per epoch the port actually had. make newentry in security/vuxml creates the vid.

  <vuln vid="FIXME (make newentry)">
    <topic>ffmpeg -- FIXME</topic>
    <affects>
      <package>
	<name>ffmpeg</name>
	<name>ffmpeg-nox11</name>
	<range><le>9.0.2_3,1</le></range>
      </package>
      <package>
	<name>ffmpeg3</name>
	<name>ffmpeg4</name>
	<range><le>9.0.2</le></range>
      </package>
    </affects>
    <description>
      <body xmlns="http://www.w3.org/1999/xhtml">
	<p>CVE-2026-125264: FFmpeg through 9.0.2 contains an uncontrolled
	  resource consumption vulnerability in parse_frame_header() in
	  libavcodec/jpegxl_parser.c that fails to validate TOC entry counts
	  against remaining input. Attackers can supply a crafted JPEG XL
	  frame header with a permuted TOC and huge toc_count, making the
	  parser loop excessively and exhaust CPU.</p>
      </body>
    </description>
    <references>
      <cvename>CVE-2026-125264</cvename>
      <url>https://nvd.nist.gov/vuln/detail/CVE-2026-125264</url>
    </references>
    <dates>
      <discovery>2026-11-09</discovery>
      <entry>2026-11-10</entry>
    </dates>
  </vuln>