Summary
Affected Versions: > 0.2.0 and < 1.0.0
Patched Versions: >= 1.0.0
Description:
The library stored confidential information, including API keys, in a local SQLite database without encryption. This behavior was not clearly documented outside of the database architecture page. Users were not given the ability to configure the database location. As a result, anyone with access to the container or host filesystem could retrieve sensitive data in plaintext by accessing the .db file.
Impact:
Unauthorized access to API keys and other confidential data if the SQLite database file was exposed.
Fixed in Version 1.0.0:
- Database is fully encrypted
- Database location is configurable
- API keys can be set via environment variables (this capability existed in earlier versions)
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-57806? CVE-2025-57806 is a medium-severity security vulnerability in local-deep-research (pip), affecting versions > 0.2.0, < 1.0.0. It is fixed in 1.0.0.
- Which versions of local-deep-research are affected by CVE-2025-57806? local-deep-research (pip) versions > 0.2.0, < 1.0.0 is affected.
- Is there a fix for CVE-2025-57806? Yes. CVE-2025-57806 is fixed in 1.0.0. Upgrade to this version or later.
- Is CVE-2025-57806 exploitable, and should I be worried? Whether CVE-2025-57806 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-57806 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-57806? Upgrade
local-deep-researchto 1.0.0 or later.