Skip to main content
VulnerabilityPublished

CVE-2024-35515: sqlitedict · Code Injection

Affects sqlitedictSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical : upgrade to 2.1.1 as a priority.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade sqlitedict to 2.1.1.

Affected software

ProductAffectedFixed in
PyPIsqlitedictpkg:pypi/sqlitedictOther threatsAffected
  • <2.1.1
Fixed in
  • 2.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-35515, organizations should immediately audit their Python environments for the presence of sqlitedict versions up to 2.1.0 and plan for an upgrade once a patched version is released. If you cannot patch yet, avoid deserializing untrusted or unauthenticated data inputs through sqlitedict. Implement strict input validation and sanitization on all data sources feeding into sqlitedict. Employ application-layer controls such as sandboxing or running vulnerable components with least privilege to limit potential damage. Monitor logs and network traffic for unusual activity indicative of exploitation attempts, such as unexpected deserialization operations or anomalous process behavior. Consider isolating services using sqlitedict from critical infrastructure until the vulnerability is resolved. Engage with the sqlitedict maintainers or community for updates and recommended fixes. Finally, incorporate secure coding practices to prevent insecure deserialization in future development.

Description

Insecure deserialization in sqlitedict up to v2.1.0 allows attackers to execute arbitrary code.

References

Community reviews

Loading reviews…