SQLite before 3.25.3, when the FTS3 extension is enabled, encounters an integer overflow (and resultant buffer overflow) for FTS3 queries th
Noroxi assessment
Priority: Monitor (action score 35/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: 10.3% (FIRST EPSS); higher than 95.6% 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.6) 3.25.3-r0; chromium (Debian:12) 71.0.3578.80-1; sqlite3 (Debian:12) 3.25.3-1.
Low priority for now. Upgrade to sqlite (Alpine:v3.6) 3.25.3-r0; chromium (Debian:12) 71.0.3578.80-1; sqlite3 (Debian:12) 3.25.3-1 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
SQLite before 3.25.3, when the FTS3 extension is enabled, encounters an integer overflow (and resultant buffer overflow) for FTS3 queries that occur after crafted changes to FTS3 shadow tables, allowing remote attackers to execute arbitrary code by leveraging the ability to run arbitrary SQL statements (such as in certain WebSQL use cases), aka Magellan.
- Published
- Dec 21, 2018
- Updated
- Jun 16, 2026
- EPSS
- 10.3% · 95th percentile
- CWE
- CWE-190
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 32 / 40 · 8.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 10.3%
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 |
| chrome | cpe:2.3:a:google:chrome | |
| redhat | linux | cpe:2.3:o:redhat:linux |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux8.0
- google chromebefore 71.0.3578.80
- opensuse leap15.0
- opensuse leap42.3
- redhat linux6.0
- sqlite sqlitebefore 3.25.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.6 | sqlite | before 3.25.3-r0 | 3.25.3-r0 |
| Debian:12 | chromium | before 71.0.3578.80-1 | 71.0.3578.80-1 |
| Debian:12 | sqlite3 | before 3.25.3-1 | 3.25.3-1 |
| Debian:8 | sqlite3 | before 3.8.7.1-1+deb8u3 | 3.8.7.1-1+deb8u3 |
| Debian:9 | sqlite3 | before 3.16.2-5+deb9u2 | 3.16.2-5+deb9u2 |
| openSUSE:Leap 15.0 | sqlite3 | before 3.27.2-lp150.2.3.1 | 3.27.2-lp150.2.3.1 |
| SUSE:HPE Helion OpenStack 8 | sqlite3 | before 3.36.0-9.18.1 | 3.36.0-9.18.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 | sqlite3 | before 3.27.2-3.3.2 | 3.27.2-3.3.2 |
| SUSE:Linux Enterprise Server 12-LTSS | sqlite3 | before 3.8.3.1-2.7.1 | 3.8.3.1-2.7.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | sqlite3 | before 3.7.6.3-1.4.7.3.1 | 3.7.6.3-1.4.7.3.1 |
| SUSE:OpenStack Cloud 7 | sqlite3 | before 3.8.10.2-9.3.1 | 3.8.10.2-9.3.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
- 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.25.3-r0 · Alpine:v3.6 | Package registry (OSV) |
| debian:chromium | 71.0.3578.80-1 · Debian:12 | Package registry (OSV) |
| debian:sqlite3 | 3.25.3-1 · Debian:12 | Package registry (OSV) |
| opensuse:sqlite3 | 3.27.2-lp150.2.3.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| suse:sqlite3 | 3.27.2-3.3.2 · SUSE:Linux Enterprise Module for Basesystem 15 | 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-190 · Integer Overflow or WraparoundCVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.opensuse.org/opensuse-security-announce/2019-04/msg00070.html
- www.securityfocus.com/bid/106323
- access.redhat.com/articles/3758321
- blade.tencent.com/magellan/index_en.html
- bugzilla.redhat.com/show_bug.cgi?id=1659379
- bugzilla.redhat.com/show_bug.cgi?id=1659677
- chromereleases.googleblog.com/2018/12/stable-channel-update-for-desktop.html
- chromium.googlesource.com/chromium/src/+/c368e30ae55600a1c3c9cb1710a54f9c55de786e
- crbug.com/900910
- kc.mcafee.com/corporate/index?page=content&id=SB10365
- lists.debian.org/debian-lts-announce/2018/12/msg00012.html
- lists.debian.org/debian-lts-announce/2020/08/msg00037.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PU4NZ6DDU4BEM3ACM3FM6GLEPX56ZQXK/
- news.ycombinator.com/item?id=18685296
- security.gentoo.org/glsa/201904-21
- sqlite.org/src/info/940f2adc8541a838
- sqlite.org/src/info/d44318f59044162e
- support.apple.com/HT209443
- support.apple.com/HT209446
Vendor advisories and official records. Exploit/PoC links are deliberately left out.