CVE-2021-22926 @ Saiph

Status

new

Priority

0.62

Match score

4.0

Risk

DoS Remote

CVSS

7.5 HIGH

Reason

cpe: curl; pkgs: curl; version: in-range: curl-7.64.0-4+deb10u9; risk:dos

Created

2026-10-15T10:20:39Z

Updated

2026-10-20T10:18:48Z

Package interrogation (copy)

Run on the host — click to copy a command. Debian/apt

Package	Commands
curl-7.64.0-4+deb10u9
libcurl3-gnutls-7.64.0-4+deb10u9
libcurl4-7.64.0-4+deb10u9

Inventory lookup

Search package inventory across systems, then return here. Create a ticket on systems the matcher missed.

Suggestions: curl

Same product CVEs in your queue

Other open tickets that look like the same product. Closed tickets are omitted unless they are already pegged to this CVE.

CVE	CVSS	Systems	Status	Matched	Already related
CVE-2022-32221	9.8	Archive, Janus, Library, Saiph, morris …	new	curl	—
CVE-2023-27534	8.8	Archive, Janus, Library, Saiph, morris …	new	curl	—
CVE-2023-27533	8.8	Archive, Janus, Library, Saiph, morris …	new	curl	—
CVE-2024-2398	8.6	Archive, Janus, Library, Saiph	new	curl	—
CVE-2021-22946	7.5	Archive, Janus, Library, Saiph, morris …	new	curl	—
CVE-2022-27782	7.5	Archive, Janus, Library, Saiph, morris …	new	curl	—
CVE-2022-27781	7.5	Archive, Janus, Library, Saiph, morris …	new	curl	—
CVE-2025-0725	7.3	Archive, Helios, Janus, Library, Matrix …	new	curl	—

Related CVE (same fix)

Point this ticket’s CVE at a higher-priority / same-fix primary so you only triage one.

Host OS / kernel

Debian GNU/Linux 10 (buster) (10) · debian

Arch

x86_64

kernel_release

uname -r → 4.19.0-27-amd64

kernel_version

uname -v → #1 SMP Debian 4.19.316-1 (2024-06-25)

For Linux kernel CVEs, kernel_version (Debian packaging / build string) often decides fixed vs not; kernel_release is used for upstream NVD range compares.

Same CVE on other hosts

Open the ticket for this CVE on another system.

System	Status	Priority	Updated
Library	new	1.75	2026-10-20T10:18:48Z	Open
Archive	new	0.62	2026-10-20T10:18:48Z	Open
Helios	new	0.62	2026-10-20T10:18:48Z	Open
Janus	new	0.62	2026-10-20T10:18:48Z	Open

Description

libcurl-using applications can ask for a specific client certificate to be used in a transfer. This is done with the `CURLOPT_SSLCERT` option (`--cert` with the command line tool).When libcurl is built to use the macOS native TLS library Secure Transport, an application can ask for the client certificate by name or with a file name - using the same option. If the name exists as a file, it will be used instead of by name.If the appliction runs with a current working directory that is writable by other users (like `/tmp`), a malicious user can create a file name with the same name as the app wants to use by name, and thereby trick the application to use the file based cert instead of the one referred to by name making libcurl send the wrong client certificate in the TLS connection handshake.

Update status