CVE-2022-26499 [Critical] | Security Vulnerability in Asterisk

An SSRF issue was discovered in Asterisk through 19.x. When using STIR/SHAKEN, it's possible to send arbitrary requests (such as GET) to interfaces such as localhost by using the Identity header. This is fixed in 16.25.2, 18.11.2, and 19.3.2.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-01	1.11%	1.46%	+0.35%
2	2026-05-22	0.66%	1.11%	+0.46%
3	2026-04-26	—	0.66%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-01

1.11%

1.46%

+0.35%

2026-05-22

0.66%

1.11%

+0.46%

2026-04-26

—

0.66%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
9.1	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:N) Service keeps running; no real outage angle.	3.9	5.2	[email protected]
6.4	2.0	MEDIUM	`AV:N/AC:L/Au:N/C:P/I:P/A:N` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:P) Partial confidentiality impact. Integrity impact (I:P) Partial integrity impact. Availability impact (A:N) No availability impact.	10.0	4.9	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

9.1

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N): Service keeps running; no real outage angle.

3.9

5.2

[email protected]

6.4

2.0

MEDIUM

AV:N/AC:L/Au:N/C:P/I:P/A:N Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:P): Partial confidentiality impact.
Integrity impact (I:P): Partial integrity impact.
Availability impact (A:N): No availability impact.

10.0

4.9

[email protected]

OS Trackers for CVE-2022-26499

vendor	priority	summary	link
`alpine`	critical	CVE-2022-26499: 1 source package rows (asterisk); 32 state rows across 8 repos (3.12-main, 3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 25.	https://security.alpinelinux.org/vuln/CVE-2022-26499
`debian`	not yet assigned	CVE-2022-26499 not yet assigned priority: Debian including 1 source packages (asterisk), 2 status rows across 2 suites (bullseye, sid): resolved 2.	https://security-tracker.debian.org/tracker/CVE-2022-26499
`gentoo`	high	CVE-2022-26499: 1 GLSA(s) (202412-03), 1 atom(s) (net-misc/asterisk); latest impact high.	https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2022-26499
`ubuntu`	medium	CVE-2022-26499 medium priority: Ubuntu including 1 source packages (asterisk), 14 status rows across 14 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, needs-triage 6, released 1.	https://ubuntu.com/security/CVE-2022-26499

Affected software / configurations for CVE-2022-26499

Vendor	Product	Version	Raw CPE
digium	asterisk	>= 16.15.0, <= 16.25.1	cpe:2.3:a:digium:asterisk::::::::
digium	asterisk	>= 18.0, < 18.11.2	cpe:2.3:a:digium:asterisk::::::::
digium	asterisk	>= 19.0.0, <= 19.3.1	cpe:2.3:a:digium:asterisk::::::::
debian	debian_linux	10.0	cpe:2.3:o:debian:debian_linux:10.0:::::::*
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*

References for CVE-2022-26499

URL	Tags
http://packetstormsecurity.com/files/166745/Asterisk-Project-Security-Advisory-AST-2022-002.html	Patch Third Party Advisory VDB Entry
https://downloads.asterisk.org/pub/security/	Vendor Advisory
https://downloads.asterisk.org/pub/security/AST-2022-002.html	Patch Vendor Advisory
https://lists.debian.org/debian-lts-announce/2022/11/msg00021.html	Issue Tracking Third Party Advisory
https://www.debian.org/security/2022/dsa-5285	Third Party Advisory

URL

CVE-2022-26499

Exploit prediction scoring system (EPSS) score for CVE-2022-26499

Common vulnerability scoring system (CVSS) metrics for CVE-2022-26499

Weakness enumeration for CVE-2022-26499

OS Trackers for CVE-2022-26499

Affected software / configurations for CVE-2022-26499

References for CVE-2022-26499