CVE-2023-42365: busybox
Affects busyboxSource CVE Database V5
Not known to be exploited.
Data as of 26 Oct 2026, 08:30 UTC
Rated Medium by the CNA (mitre) · No CVSS score from NVD or the CNA
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 27 Nov 2023
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Alpinealpine/busyboxpkg:apk/alpine/busyboxOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should monitor the vendor advisory for updates and apply any official fixes once released. Until then, avoid processing untrusted awk patterns with BusyBox 1.36.1 to reduce risk.
Description
A use-after-free vulnerability exists in BusyBox version 1.36.1 in the awk.c copyvar function triggered by a crafted awk pattern. This flaw could potentially lead to undefined behavior or memory corruption when processing malicious input.