CVE-2021-22946
A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (`--ssl-req
CVSS
7.5
Alto
EPSS
4.5%
p92
KEV
—
Exploit Today
28
0-100
Publicado: 29 sept 2021 · Última mod.: 14 oct 2026 · CWE-325 · CWE-319
4.5%EPSS · 30 días4.5%
2026-10-172026-11-13
A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (`--ssl-reqd` on the command line or`CURLOPT_USE_SSL` set to `CURLUSESSL_CONTROL` or `CURLUSESSL_ALL` withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations **withoutTLS** contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.
- seclists.orghttp://seclists.org/fulldisclosure/2022/Mar/29
- cert-portal.siemens.comhttps://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- hackerone.comhttps://hackerone.com/reports/1334111
- lists.debian.orghttps://lists.debian.org/debian-lts-announce/2021/09/msg00022.html
- lists.debian.orghttps://lists.debian.org/debian-lts-announce/2022/08/msg00017.html
- lists.fedoraproject.orghttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/APOAK4X73EJTAPTSVT7IRVDMUWVXNWGD/
- lists.fedoraproject.orghttps://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/RWLEC6YVEM2HWUBX67SDGPSY4CQB72OE/
- security.gentoo.orghttps://security.gentoo.org/glsa/202212-01
- security.netapp.comhttps://security.netapp.com/advisory/ntap-20211029-0003/
- security.netapp.comhttps://security.netapp.com/advisory/ntap-20220121-0008/
- support.apple.comhttps://support.apple.com/kb/HT213183
- www.debian.orghttps://www.debian.org/security/2022/dsa-5197
- www.oracle.comhttps://www.oracle.com/security-alerts/cpuapr2022.html
- www.oracle.comhttps://www.oracle.com/security-alerts/cpujan2022.html
- www.oracle.comhttps://www.oracle.com/security-alerts/cpujul2022.html
- www.oracle.comhttps://www.oracle.com/security-alerts/cpuoct2021.html
- seclists.orghttp://seclists.org/fulldisclosure/2022/Mar/29
- cert-portal.siemens.comhttps://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf
- hackerone.comhttps://hackerone.com/reports/1334111
- lists.debian.orghttps://lists.debian.org/debian-lts-announce/2021/09/msg00022.html
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-61810—3.3%
——1libspdm is a sample implementation that follows the DMTF SPDM specifications. In version 1.4.0, both the FINISH request (Table 80) and the FINISH_RSP response (Table 81) gained two new fields, OpaqueDataLength and OpaqueData, placed before the trailing signed/authenticated field. The transcript definitions used to compute and verify the FINISH signature, the FINISH HMAC (RequesterVerifyData), and the FINISH_RSP HMAC (ResponderVerifyData) were not updated and still terminate with a step of the form. Per DSP0274, the "SPDM Header Fields" are only the four header bytes (SPDMVersion, RequestResponseCode, Param1, Param2). A literal reading therefore excludes OpaqueDataLength and OpaqueData, even though those fields are transmitted before the trailing signature/HMAC field. Because the signature/HMAC must cover every field transmitted before it to "protect the entire handshake against manipulation by an active attacker," an active attacker could otherwise modify the opaque data in flight without invalidating the signature or HMAC. This issue has been patched in version 1.4.1.2dCVE-2026-595864.0 MED6.3%
——2In multiple locations, there is a possible way to recover cryptographic keys and forge authentication tags due to improperly used crypto. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.2dCVE-2026-88823—3.6%
——1Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional
Authenticated Data (AAD) update as a reset of all the AAD supplied so far,
instead of leaving the AAD unchanged. An application that supplies its AAD in
several fragments, one of which is empty, therefore produces or verifies
messages whose authentication tag does not cover the AAD supplied before
the empty fragment.
Impact summary: Data an application intended to authenticate alongside a
message is silently left unauthenticated. An attacker can forge the AAD of such
a message.
CWE: CWE-325: Missing Cryptographic Step
Description: An application passing AAD in multiple chunks of which some have
zero length will have the previous AAD chunks effectively unauthenticated. Also,
on context re-initialisation, the AAD was not reset, which meant that any AAD
accumulated from the previous context usage were also included in the AAD of the
new message.
The fix makes a zero-length AAD update a no-op and clears any accumulated AAD
whenever the context is re-initialised with a key or a nonce.
A re-initialisation that only changes parameters keeps the AAD.
FIPS impact: no
The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved
algorithm and is implemented only in the default provider, outside the
OpenSSL FIPS module boundary.5dCVE-2026-181286.8 MED39.1%
——12Cleartext transmission of sensitive information in the Agent of Ivanti Endpoint Manager before version 2024 SU8 allows a remote unauthenticated attacker to in a MITM position to read and modify HTTP traffic.3dCVE-2026-124600—9.5%
——3GV-Face transmits sensitive user credentials and
related authentication data over unencrypted HTTP connections. The HTTP
traffic is not encrypted, an attacker with the ability to intercept network
traffic.3dCVE-2026-1153388.1 ALT4.8%
——1Insufficient protection of communications in Progress WS_FTP Server versions prior to 2025.0.5 could allow a network attacker to intercept sensitive information or modify requests when unencrypted connections are used.4d