EM-20261111-E50Q
VulnerabilityHigh severity
BusyBox Vulnerability (CVE-2026-124739)
CVE-2026-124739
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 11 09:15 UTCC41 Red Hat Security Data
- Page Born
- Nov 11 11:17 UTCsecond source joined
- Last Signal
- Nov 11 11:17 UTC12 hours before snapshot
- Sources
- 21 official · 1 research, news or crowd
- Open For
- 3 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The ID never changes, and earlier addresses keep working. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 11 11:17 UTCC6 NVD published
- Scored: reachedNov 11 11:17 UTCCVSS 7.5
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: reachedNov 11 09:15 UTCC41 published
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- CVE-2026-124739 (CVSS 7.5) (opens source in a new tab) 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… High severityDatabaseC6 NVD CVE API 2.0
- Red Hat: CVE-2026-124739 (important) (opens source in a new tab) busybox: httpd stack buffer overflow via an "I:" rule in a subdirectory httpd.conf High severityVendorC41 Red Hat Security Data