---
id: "CVE-2026-57195"
kind: "vulnerability"
aliases: ["CVE-2026-57195"]
title: "Asterisk: NULL pointer dereference in AMI over HTTP crashes the server"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["asterisk", "package", "self-hosted", "telephony", "voip"]
not_affected_if: ["ami-http-disabled", "default-config", "http-disabled"]
published_at: "2026-10-27T21:18:06+00:00"
first_seen_at: "2026-10-27T21:29:22+00:00"
updated_at: "2026-10-27T21:30:20+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-57195", "first_seen_at": "2026-10-27T21:29:22+00:00"}]
---

# Asterisk: NULL pointer dereference in AMI over HTTP crashes the server

A NULL pointer dereference in the Asterisk Manager Interface, reached over HTTP with Digest Authentication, lets an unauthenticated attacker crash Asterisk. The sources describe a denial of service, not code execution.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Run `asterisk -rx "core show version"` to read the installed version.
- Check `http.conf` for `enabled=yes` and `manager.conf` for `enabled=yes` and `webenabled=yes`; all three must be on for exposure.
- Check the HTTP bind address in `http.conf`; the default is `127.0.0.1`.

## Fix

- Upgrade Asterisk to `20.20.1`, `21.12.3`, `22.10.1` or `23.4.1`, or Certified Asterisk to `20.7-cert11` or `22.8-cert3`.
- If an upgrade is not possible, disable AMI over HTTP (`webenabled=no` in `manager.conf`) or disable the HTTP server.

## Timeline

- 2026-10-27T21:29:22+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-57195

## From the sources

Asterisk is an open source private branch exchange and telephony toolkit. Prior to Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3, a NULL pointer dereference in the `Asterisk Manager Interface (AMI)` may allow an unauthenticated attacker to crash Asterisk when `Digest Authentication` is used via `HTTP`. The Asterisk `HTTP` web server, AMI, and AMI access via `HTTP` must all be enabled; each is disabled by default. The attacker must be able to connect to the `HTTP` server, which binds only to `127.0.0.1` by default even when enabled. This issue is fixed in Asterisk 20.20.1, 21.12.3, 22.10.1, 23.4.1 and Certified Asterisk 20.7-cert11, 22.8-cert3.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_