CVE-2026-124739 json
Busybox: httpd stack buffer overflow via an "i:" rule in a subdirectory httpd.conf
published yesterday modified 14h ago also EUVD-2026-123348
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
A flaw was found in BusyBox. When the httpd web server processes subdirectory configuration files, an overly long index page name can trigger a stack-based buffer overflow. An attacker with permissions to write to a subdirectory configuration file could exploit this vulnerability to execute arbitrary code with elevated privileges or cause a denial of service (DoS) by crashing the server process.
Is CVE-2026-124739 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-124739 updated cvss 7.5
busybox: httpd stack buffer overflow via an "I:" rule in a subdirectory httpd.conf
-
Red Hat Enterprise Linux 6 busybox, busybox-petitboot Red Hat Hardened Images busyboxaffected: workaround, no fix available
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Red Hat Red Hat Enterprise Linux 6
- Red Hat Red Hat Hardened Images
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
access.redhat.com
/security/cve/CVE-2026-124739
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2571613
issue-tracking
Sources
- CVE List CVE-2026-124739
- NVD CVE-2026-124739
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.