Skip to content
Fencer Vulns
high 7.5

CVE-2022-26498 in the critical feed json

An issue was discovered in Asterisk through 19.x.

published 2022-04-15 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-31056

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
16.5%
EPSS 16.5% chance of exploitation in 30 days, percentile 97%
public exploits
0
none known

Summary

An issue was discovered in Asterisk through 19.x. When using STIR/SHAKEN, it is possible to download files that are not certificates. These files could be much larger than what one would expect to download, leading to Resource Exhaustion. This is fixed in 16.25.2, 18.11.2, and 19.3.2.

Patch / fix

  • digium asterisk 18.11.2
  • asterisk Debian 14 1:18.11.2~dfsg+~cs6.10.40431413-1

debian advisories DEBIAN-CVE-2022-26498

  • asterisk Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 18.11.2-r0

alpine advisories ALPINE-CVE-2022-26498

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-26498 updated

asterisk: multiple vulnerabilities

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

16.52% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.