CVE-2026-57195

validatedZero produced an exploit or a check.

GHSA-3rhj-hhw7-m6fw ↗EUVD-2026-111393 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
asterisk <= 20.20.0; <= 21.12.2; <= 22.10.0; <= 23.4.0; <= 20.7-cert10; <= 22.8-cert2
fixed in 20.20.1, 21.12.3, 22.10.1, 23.4.1, 20.7-cert11, 22.8-cert3
CWE-476 NULL Pointer Dereference
ETK-2026-2803Zero's internal tracking ID, independent of the CVE number., permanent identifier
+2h11mTTV
26mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+2h11magent stopped
0
+1h
+2h

description

Asterisk releases before 20.20.1, 21.12.3, 22.10.1, or 23.4.1, and Certified Asterisk releases before 20.7-cert11 or 22.8-cert3, can be crashed through AMI over HTTP using Digest Authentication. Exposure requires the HTTP server, AMI, and AMI HTTP access to be enabled, and the attacker must be able to reach the HTTP listener.

mitigation

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. Until upgraded, disable AMI access over HTTP where it is not required and restrict the HTTP listener to trusted hosts.

fixed in 20.20.1, 21.12.3, 22.10.1, 23.4.1, 20.7-cert11, 22.8-cert3

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
deterministic
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 21:04Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-27 21:04Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-57195

{
  "etk_id": "ETK-2026-2803",
  "cve_id": "CVE-2026-57195",
  "display_id": "CVE-2026-57195",
  "ghsa_id": "GHSA-3rhj-hhw7-m6fw",
  "euvd_id": "EUVD-2026-111393",
  "status": "published",
  "anchor_state": "anchored",
  "title": "NULL pointer dereference in Asterisk HTTP AMI authentication",
  "summary": "Asterisk releases before 20.20.1, 21.12.3, 22.10.1, or 23.4.1, and Certified Asterisk releases before 20.7-cert11 or 22.8-cert3, can be crashed through AMI over HTTP using Digest Authentication. Exposure requires the HTTP server, AMI, and AMI HTTP access to be enabled, and the attacker must be able to reach the HTTP listener.",
  "mitigation": "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. Until upgraded, disable AMI access over HTTP where it is not required and restrict the HTTP listener to trusted hosts.",
  "vendor": "asterisk",
  "product": "asterisk",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 20.20.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "20.20.1"
      ],
      "package_name": "asterisk",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 21.12.2"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "21.12.3"
      ],
      "package_name": "asterisk",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 22.10.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "22.10.1"
      ],
      "package_name": "asterisk",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 23.4.0"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "23.4.1"
      ],
      "package_name": "asterisk",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 20.7-cert10"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "20.7-cert11"
      ],
      "package_name": "certified-asterisk",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 22.8-cert2"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "22.8-cert3"
      ],
      "package_name": "certified-asterisk",
      "purl": null
    }
  ],
  "cwes": [
    476
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 25.55590825,
  "t0_at": "2026-10-27T21:04:25.747000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-27T23:15:26.895547+00:00",
      "days": 0.09098551559027777,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T21:04:25.747000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-27T21:04:25.747000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T21:04:25.747000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-57195"
    }
  }
}

published 2026-10-27 22:49Z
last change 2026-10-28 00:11Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.