Deserialization of untrusted data for some BigDL software before version 2.5.0b1 within Ring 3: User Applications may
Source GCVE Database
Not known to be exploited · CVSS 6.9 Medium.
Data as of 10 Nov 2026, 19:18 UTC
Thin evidence
One scorer or none| CNA (intel) | CVSS 4.0 | 6.9 |
|---|
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 10 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 10 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| BigDL software | Affected
| Fixed in– |
AI-suggested
Until a patch is available, restrict network access to vulnerable components and monitor for unusual activity related to deserialization processes.
Description
A deserialization vulnerability exists in some BigDL software versions prior to 2.5.0b1 within Ring 3. This flaw may allow an unauthenticated, unprivileged attacker to escalate privileges via network access without user interaction. The impact on confidentiality, integrity, and availability is rated low, with no subsequent system-level impacts expected. The vulnerability is tracked as CVE-2026-52899 with a medium severity rating and a CVSS 4.0 score of 6.9.