Vulnary
← back to the feed
Critical· 9.1

CVE-2026-51300

A use‑after‑free flaw in SQLite 3.41 lets a remote attacker craft SQL queries that cause the program to access memory that has already been freed. This can crash the application and expose sensitive data from memory. The issue is serious enough to receive a CVSS score of 9.1.

publishedJul 27, 2026
last modifiedJul 28, 2026
sourcesNVD
severity · cvss
9.1
critical · how bad it is
exploitation · epss
<1%
33th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 11, 2026

No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.

01

Who is affected

SQLite 3.41, used by many applications that embed the database engine.

02

Real-world impact

An attacker could cause the target application to crash and potentially read confidential information from memory, which could be used for further attacks.

03

Why this severity

The CVSS score of 9.1 reflects the vulnerability’s high impact: it requires no user interaction, no privileges, and can lead to complete loss of confidentiality and availability. The attack is straightforward over the network and can be executed remotely.

04

What to do about it

no official fix yet

No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.

No fix documented in sources

05

Timeline

06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredNone
User interactionNone needed
ScopeUnchanged
Confidentiality impactHigh
Integrity impactNone
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →