BlackTreeCVE IntelligenceUnknown · Sqlite3
Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Alpine v3.23v3.23 · main | sqlite | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.28.0-r0 | Alpine Security Database ↗Source updated 23 Oct 2026 |
| Alpine v3.22v3.22 · main | sqlite | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.28.0-r0 | Alpine Security Database ↗Source updated 23 Oct 2026 |
| Alpine v3.21v3.21 · main | sqlite | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 3.28.0-r0 | Alpine Security Database ↗Source updated 23 Oct 2026 |
| Debian trixietrixie · source | sqlite3 | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.27.2-3 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian bookwormbookworm · source | sqlite3 | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.27.2-3 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian forkyforky · source | sqlite3 | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.27.2-3 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian sidsid · source | sqlite3 | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.27.2-3 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
The vendor explicitly identifies these products or versions as containing the fix.
The vendor explicitly identifies these products as affected by this CVE.
High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 5 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by productAn 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.
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.
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
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.
The program can continue using memory after it has been released, producing unsafe and attacker-influenceable behaviour.
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.
CWE-416: Use After Free. The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory belongs to the code that operates on the new pointer.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 10 May 2019 · Last source change 14 Oct 2026, 06:35 UTC · CWE-416 · Use After Free
Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.