Vulnerability · AZL-109773
CVE-2026-88842 affecting package busybox 1.36.1-27
Published Oct 14, 2026 · catalog updated Oct 21, 2026 · affecting package busybox 1.36.1-27
Open the advisory
Exploitation likelihood is not on this record for AZL-109773. A missing EPSS score is not a low risk. Compare affecting package busybox 1.36.1-27 with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (affecting package busybox 1.36.1-27).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Awaiting synchronization with FIRST
- Remediation
- Not established
- Affected products
- Azure Linux:3 busybox
A flaw was found in BusyBox dpkg. The write_status_file() function does not reset a field cursor between package stanzas. When two packages are removed in a single invocation and the first stanza is larger than the second, the second package stanza can be dropped from the status file, causing limited data corruption.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Azure Linux:3 busybox0 → 1.36.1-27
How to fix AZL-109773
Recommended remediation
No required-action text, fix commit, or clear fixed-version range is stored yet.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for AZL-109773. A missing EPSS score is not a low risk. Compare affecting package busybox 1.36.1-27 with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with 0 → 1.36.1-27. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 14, 2026 · OpenSSF OSV / OSV Scanner
Detected
A flaw was found in BusyBox dpkg. The write_status_file() function does not reset a field cursor between package stanzas. When two packages are removed in a single invocation and the first stanza is larger than the second, the second package stanza can be dropped from the status file, causing limited data corruption.
Oct 21, 2026 · OpenSSF OSV / OSV Scanner
Fix available
busybox fixed in 1.36.1-27
Oct 21, 2026 · OpenSSF OSV / OSV Scanner
Updated
A flaw was found in BusyBox dpkg. The write_status_file() function does not reset a field cursor between package stanzas. When two packages are removed in a single invocation and the first stanza is larger than the second, the second package stanza can be dropped from the status file, causing limited data corruption.
Sources
- OpenSSF OSV / OSV ScannerPackage advisoryAZL-109773
CVE-2026-88842 affecting package busybox 1.36.1-27
osv.dev
References
Freshness
Last verified in this catalog Oct 21, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.