CVE-2026-124737

Busybox: heap buffer overflow in the tftp client on fallback to the default block size

  • High 7.5

Description

A flaw was found in BusyBox. When the TFTP (Trivial File Transfer Protocol) client requests a custom small block size and receives a standard response, it falls back to the default block size without resizing the allocated memory buffer. A malicious TFTP server can exploit this issue by sending standard-sized network packets during a transfer, causing a heap buffer overflow. This flaw allows an attacker to achieve arbitrary code execution or cause a Denial of Service (DoS) by crashing the application.

Key facts

Published
11 Nov 2026
Last changed
11 Nov 2026
Assigned by
redhat
EPSS
0.454% likely to be exploited in the next 30 days, higher than 39.931% of CVEs (scores for 15 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.5CVSS 3.1, Highfrom the CNA (redhat)CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

What to do

  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.CNA workaround statement

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
Red HatRed Hat Enterprise Linux 6
  • Default status: affected
Red HatRed Hat Hardened Images
  • Default status: affected

Timeline

  1. 25 Oct 2026 Reported to Red Hat.
  2. 11 Nov 2026 Made public.
  3. 11 Nov 2026 Published

Weakness

References