Quick answers
- Is CVE-2026-88836 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88836 being exploited in the wild.
- How severe is CVE-2026-88836?
- Informational severity, published 13 October 2026.
- Which products and versions are affected?
- BusyBox <UNKNOWN>.
- Is there a fix for CVE-2026-88836?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-88836 attacked?
- It is in a software library.
- Am I affected by CVE-2026-88836?
- Check whether you run BusyBox at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
BusyBox's FEATURE_WGET_HTTPS implements a minimal TLS stack that intentionally skips peer identity verification and other full TLS security measures. The missing Finished message verify_data checking in the TLS handshake completion is a design choice documented in the feature documentation, not a defect crossing a separate security boundary. Red Hat Product Security assessed this as a design limitation rather than a security vulnerability.
Affected products
- BusyBox <UNKNOWN>
Timeline
- 2026-10-13: disclosed