How severe is CVE-2022-35737?

CVE-2022-35737 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-35737?

CVE-2022-35737 affects the following packages: libsqlite3-sys (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2022-35737?

Update libsqlite3-sys to 0.25.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35737 is resolved across your whole dependency graph.

How do I detect CVE-2022-35737 in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libsqlite3-sys. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2022-35737 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2022-35737?

O3 pinpoints whether CVE-2022-35737 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2022-35737 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2022-35737, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-35737?

CVE-2022-35737 has an EPSS (Exploit Prediction Scoring System) score of 11.4%, placing it in the 95th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2022-35737?

CVE-2022-35737 is classified as CWE-129 (CWE-129). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-35737 published, and has it been updated?

CVE-2022-35737 was published on August 3, 2022 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

CVE-2022-35737

HIGH

`libsqlite3-sys` via C SQLite improperly validates array index

Also known asBIT-sqlite-2022-35737GHSA-jw36-hf63-69r9RUSTSEC-2022-0090

Published

Aug 3, 2022

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

11.4%probability of exploitation in next 30 days

Moderate Risk95th percentile-43.41%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🦀libsqlite3-sys

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`libsqlite3-sys`	all versions	0.25.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bou…

github.comGithubOct 2022

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bou…

blog.trailofbits.comNVDOct 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for libsqlite3-sys. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update libsqlite3-sys to 0.25.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35737 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2022-35737 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-35737. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

SQLite 1.0.12 through 3.39.x before 3.39.2 sometimes allows an array-bounds overflow if billions of bytes are used in a string argument to a C API.

O3 Security · Impact-Aware SCA

Is CVE-2022-35737 in your dependencies?

O3 detects CVE-2022-35737 across crates.io dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works