Quick answers
- Is CVE-2026-52899 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52899 being exploited in the wild.
- How severe is CVE-2026-52899?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Intel BigDL before 2.5.0b1.
- Is there a fix for CVE-2026-52899?
- No fixed version is recorded yet. Intel recommends users uninstall BigDL or discontinue its use immediately, as the software is no longer supported with security updates. 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-52899 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-52899?
- Check whether you run Intel BigDL 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.
How to fix
Intel recommends users uninstall BigDL or discontinue its use immediately, as the software is no longer supported with security updates.
Technical details
CVE-2026-52899 is a deserialization vulnerability in BigDL before 2.5.0b1 affecting Ring 3 user applications. An unprivileged, unauthenticated attacker can exploit this via network access with low attack complexity to escalate privileges. Intel announced product discontinuation instead of releasing a security update.
Affected products
- Intel BigDL before 2.5.0b1
Timeline
- 2026-11-10: advisory