An exploitable use after free vulnerability exists in the window function functionality of Sqlite3 3.26.0.
Noroxi assessment
Priority: Monitor (action score 34/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: 6.6% (FIRST EPSS); higher than 93.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: sqlite (Alpine:v3.10) 3.28.0-r0; sqlite3 (Debian:12) 3.27.2-3; lemon (Red Hat:enterprise_linux:8::appstream) 0:3.26.0-11.el8.
Low priority for now. Upgrade to sqlite (Alpine:v3.10) 3.28.0-r0; sqlite3 (Debian:12) 3.27.2-3; lemon (Red Hat:enterprise_linux:8::appstream) 0:3.26.0-11.el8 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 exploitable use after free vulnerability exists in the window function functionality of Sqlite3 3.26.0. A specially crafted SQL command can cause a use after free vulnerability, potentially resulting in remote code execution. An attacker can send a malicious SQL command to trigger this vulnerability.
- Published
- May 10, 2019
- Updated
- Oct 14, 2026
- EPSS
- 6.6% · 93th percentile
- CWE
- CWE-416
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.6%
CNA vs NVD score
- NVD
- 8.1
- CNA · talos
- 8.1
- agree
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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 |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux19.04
- canonical ubuntu linux19.10
- sqlite sqlite3.26.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (talos). Independent of NVD's CPE analysis and usually ahead of it.
n/a Sqlite3
- SQLite 3.26.0, 3.27.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | sqlite | before 3.28.0-r0 | 3.28.0-r0 |
| Debian:12 | sqlite3 | before 3.27.2-3 | 3.27.2-3 |
| Red Hat:enterprise_linux:8::appstream | lemon | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | lemon-debuginfo | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-analyzer-debuginfo | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-debuginfo | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-debugsource | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-libs-debuginfo | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::appstream | sqlite-tcl-debuginfo | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::baseos | sqlite | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::baseos | sqlite-devel | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::baseos | sqlite-doc | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
| Red Hat:enterprise_linux:8::baseos | sqlite-libs | before 0:3.26.0-11.el8 | 0:3.26.0-11.el8 |
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 SQLite49Plan
- 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
- CVE-2020-11656In SQLite through 3.31.1, the ALTER TABLE implementation has a use-after-free, as demonstrated by an ORDER BY clause that belongs to a compo42Plan
- CVE-2017-10989The getNodeSize function in ext/rtree/rtree.c in SQLite through 3.19.3, as used in GDAL and other products, mishandles undersized RTree blob42Plan
- CVE-2019-19646pragma.c in SQLite through 3.30.1 mishandles NOT NULL in an integrity_check PRAGMA command in certain cases of generated columns.41Plan
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 |
|---|---|---|
| alpine:sqlite | 3.28.0-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:sqlite3 | 3.27.2-3 · Debian:12 | Package registry (OSV) |
| red hat:lemon | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:lemon-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-analyzer-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-debugsource | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-devel | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-doc | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-libs | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::baseos | Package registry (OSV) |
| red hat:sqlite-libs-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:sqlite-tcl-debuginfo | 0:3.26.0-11.el8 · Red Hat:enterprise_linux:8::appstream | 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.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);Fixed
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);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 (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.