Skip to main content
CVE-2025-3277VulnerabilityPublished Updated

CVE-2025-3277: sqlite · Heap-based Buffer Overflow

Affects sqliteSource CVE Database V5

0

Not known to be exploited · CVSS 6.9 Medium : upgrade to 3.49.1 when convenient.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.49.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Apr 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Upgrade sqlite to 3.49.1.

Affected software

ProductAffectedFixed in
SQLite sqliteAffected
  • <3.49.1
Fixed in
  • 3.49.1

AI-suggested

European organizations should prioritize identifying all software and devices using SQLite versions earlier than 3.49.1. In the interim, mitigating controls include: 1) Implementing strict input validation and sanitization to prevent malicious inputs from reaching the `concat_ws()` function; 2) Employing application-layer firewalls or intrusion prevention systems to detect and block suspicious payloads targeting SQLite; 3) Restricting network access to services using vulnerable SQLite instances to trusted sources only; 4) Conducting thorough code audits and penetration testing focusing on database interaction points; 5) Planning for rapid deployment of patches once available; 6) Utilizing runtime protections such as heap overflow detection and memory safety tools where possible; 7) Isolating critical systems to limit lateral movement in case of compromise. Organizations should also engage with software vendors to ensure timely updates and consider alternative database solutions if patching is delayed.

Description

An integer overflow can be triggered in SQLite’s `concat_ws()` function. The resulting, truncated integer is then used to allocate a buffer. When SQLite then writes the resulting string to the buffer, it uses the original, untruncated size and thus a wild Heap Buffer overflow of size ~4GB can be triggered. This can result in arbitrary code execution.

References

Community reviews

Loading reviews…