CVE-2026-56440 · Package
NO FIX YET · SEE WHAT TO DO
BigDL versions before 2.5.0b1 have an input validation flaw in user applications running in Ring 3. A local, unprivileged software adversary can use it to escalate privileges, and the sources describe only low impact to confidentiality, integrity and availability.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams running BigDL versions before 2.5.0b1 where untrusted local software or users can reach the application. The sources do not describe the exact data path or configuration that makes it exploitable. Teams not running BigDL can skip it.
Not affected if bigdl-2.5.0b1-or-later
Who cares bigdl, machine-learning, python
pip show bigdl or the version pinned in your requirements file2.5.0b1Improper input validation for some BigDL before version 2.5.0b1 within Ring 3: User Applications may allow an escalation of privilege. Unprivileged software adversary with an unauthenticated user combined with a low complexity attack may enable escalation of privilege. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires active user interaction. The potential vulnerability may impact the confidentiality (low), integrity (low) and availability (low) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.
This page as .md · .json · CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.