CVE-2025-70873: An information disclosure issue in the zipfileInflate function in the zipfile extension in SQLite v3.51.1 and earlier allows attackers to ob
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: azl3 sqlite 3.44.0-2 on Azure Linux 3.0 3.44.0-3; cbl2 sqlite 3.39.2-4 on CBL Mariner 2.0 3.39.2-5; Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.83.
Low priority for now. Upgrade to azl3 sqlite 3.44.0-2 on Azure Linux 3.0 3.44.0-3; cbl2 sqlite 3.39.2-4 on CBL Mariner 2.0 3.39.2-5; Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 15.9.83 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An information disclosure issue in the zipfileInflate function in the zipfile extension in SQLite v3.51.1 and earlier allows attackers to obtain heap memory via supplying a crafted ZIP file.
- Published
- Mar 12, 2026
- Updated
- Oct 15, 2026
- EPSS
- 0.4% · 39th percentile
- CWE
- CWE-244
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sqlite | sqlite | cpe:2.3:a:sqlite:sqlite |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sqlite sqlitebefore 3.51.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | sqlite3 | from 0 | — |
| openSUSE:Leap 15.6 | sqlite3 | before 3.51.3-150000.3.39.1 | 3.51.3-150000.3.39.1 |
| openSUSE:Leap 16.0 | sqlite3 | before 3.51.3-160000.1.1 | 3.51.3-160000.1.1 |
| openSUSE:Tumbleweed | sqlite3 | before 3.51.3-1.1 | 3.51.3-1.1 |
| Red Hat:hummingbird:1 | sqlite | before 0:3.52.0-1.1.hum1 | 0:3.52.0-1.1.hum1 |
| Red Hat:hummingbird:1 | sqlite-analyzer | before 0:3.52.0-1.1.hum1 | 0:3.52.0-1.1.hum1 |
| Red Hat:hummingbird:1 | sqlite-debug | before 0:3.52.0-1.1.hum1 | 0:3.52.0-1.1.hum1 |
| Red Hat:hummingbird:1 | sqlite-devel | before 0:3.52.0-1.1.hum1 | 0:3.52.0-1.1.hum1 |
| Red Hat:hummingbird:1 | sqlite-doc | before 0:3.52.0-1.1.hum1 | 0:3.52.0-1.1.hum1 |
| Red Hat:hummingbird:1 | sqlite-libs | before 0:3.52.0-1.1.hum1 | 0:3.52.0-1.1.hum1 |
| Red Hat:hummingbird:1 | sqlite-tcl | before 0:3.52.0-1.1.hum1 | 0:3.52.0-1.1.hum1 |
| Red Hat:hummingbird:1 | sqlite-tools | before 0:3.52.0-1.1.hum1 | 0:3.52.0-1.1.hum1 |
| SUSE:Linux Enterprise Micro 5.3 | sqlite3 | before 3.51.3-150000.3.39.1 | 3.51.3-150000.3.39.1 |
| SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | sqlite3 | before 3.51.3-9.47.1 | 3.51.3-9.47.1 |
| SUSE:Linux Micro 6.0 | sqlite3 | before 3.51.3-1.1 | 3.51.3-1.1 |
| SUSE:Linux Micro 6.1 | sqlite3 | before 3.51.3-slfo.1.1_1.1 | 3.51.3-slfo.1.1_1.1 |
| SUSE:Linux Micro 6.2 | sqlite3 | before 3.51.3-160000.1.1 | 3.51.3-160000.1.1 |
Same product
sqlite: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-8457SQLite3 from 3.6.0 to and including 3.27.2 is vulnerable to heap out-of-bound read in the rtreenode() function when handling invalid rtree t53Plan
- CVE-2025-6965Integer Truncation on SQLite50Plan
- CVE-2015-5895Multiple unspecified vulnerabilities in SQLite before 3.8.10.2, as used in Apple iOS before 9, have unknown impact and attack vectors.43Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-3277Apr 14, 2025 · An integer overflow can be triggered in SQLite’s `concat_ws()` function.27Monitor
- ← EarlierCVE-2025-7458Jul 29, 2025 · SQLite integer overflow in key info allocation may lead to information disclosure.27Monitor
- Later →CVE-2026-11822Jun 9, 2026 · SQLite before 3.53.2 Memory Corruption in FTS5 Extension34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| azl3 sqlite 3.44.0-2 on Azure Linux 3.0 | 3.44.0-3 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 sqlite 3.39.2-4 on CBL Mariner 2.0 | 3.39.2-5 · CBL-Mariner Releases | Microsoft (MSRC) |
| Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) | 15.9.83 · Release Notes | Microsoft (MSRC) |
| Microsoft Visual Studio 2019 version 16.11 (includes 16.0 - 16.10) | 16.11.60 · Release Notes | Microsoft (MSRC) |
| Microsoft Visual Studio 2022 version 17.14 | 17.14.40 · Release Notes | Microsoft (MSRC) |
| Microsoft Visual Studio 2026 version 18.9 | 18.9.3 · Release Notes | Microsoft (MSRC) |
| opensuse:sqlite3 | 3.51.3-150000.3.39.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| red hat:lemon | 0:3.52.0-1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:sqlite | 0:3.52.0-1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:sqlite-analyzer | 0:3.52.0-1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:sqlite-debug | 0:3.52.0-1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:sqlite-devel | 0:3.52.0-1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:sqlite-doc | 0:3.52.0-1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:sqlite-libs | 0:3.52.0-1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:sqlite-tcl | 0:3.52.0-1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:sqlite-tools | 0:3.52.0-1.1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| suse:sqlite3 | 3.51.3-150000.3.39.1 · SUSE:Linux Enterprise Micro 5.3 | Package registry (OSV) |
| suse:sqlite3 | 3.51.3-9.47.1 · SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-244 · Improper Clearing of Heap Memory Before Release ('Heap Inspection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.