BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2021
CVE-2021-22926High confidence

libcurl-using applications can ask for a specific client certificate to be used in a transfer

Unknown · https://github.com/curl/curl

Official source article: Siemens SSA-398330 ↗. Check the applicable product and release in the original source.

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:Critical, raised one band.upgradedsince 28 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 9.82% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Unknown https://github.com/curl/curl and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

4 current
CVE-2021-22926 · CSAF 2.0 · revision 15 · interimSUSE Product Security TeamCVE-2021-22926
196 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • curl as component of HPE Helion OpenStack 8
  • libcurl4 as component of HPE Helion OpenStack 8
  • libcurl4-32bit as component of HPE Helion OpenStack 8
  • curl as component of SUSE CaaS Platform 4.0
  • libcurl-devel as component of SUSE CaaS Platform 4.0
  • libcurl4 as component of SUSE CaaS Platform 4.0
  • libcurl4-32bit as component of SUSE CaaS Platform 4.0
  • curl as component of SUSE Enterprise Storage 6
  • curl as component of SUSE Enterprise Storage 7.1
  • libcurl-devel as component of SUSE Enterprise Storage 7.1
  • libcurl4 as component of SUSE Enterprise Storage 7.1
  • libcurl4-32bit as component of SUSE Enterprise Storage 7.1
Summary
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.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-398330 · CSAF 2.0 · revision 18 · interimSiemens ProductCERTSSA-398330: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP >= V3.1.0 and < V3.1.5
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0)
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0)
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0)
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0)
Summary
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.
Remediation
Update to V3.1.5 or later version
SCA-2022-0011 · CSAF 2.0 · revision 3 · finalSICK PSIRTVulnerabilities in SICK Package Analytics
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SICK Package Analytics <4.4
Summary
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 application 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.
Remediation
The patch and installation procedure for the software update is available from the responsible SICK customer contact person.
SSA-389290 · CSAF 2.0 · revision 1 · finalSiemens ProductCERTSSA-389290: Third-Party Component Vulnerabilities in SINEC INS
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SINEC INS
Summary
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.
Remediation
Update to V1.0.1.1 or later version
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-10055

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → vulnerable operation → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-840 ↗

CWE-840. Open the MITRE definition for the exact weakness description.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-840Public exploit reference
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-0180Dell Data Protection Advisor: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell Data Protection Advisor ausnutzen, um beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, Sicherheitsmaßnahmen zu umgehen und nicht näher spezifizierte Angriffe zu starten.

Official advisory ↗
BSI · German · WID-SEC-2023-2229Splunk Splunk Enterprise: Mehrere Schwachstellen

Ein entfernter, authentifizierter Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise ausnutzen, um beliebigen Code auszuführen, einen 'Denial of Service'-Zustand zu verursachen, seine Privilegien zu erweitern und weitere, nicht spezifizierte Auswirkungen zu verursachen.

Official advisory ↗
BSI · German · WID-SEC-2022-0432Xerox FreeFlow Print Server: Mehrere Schwachstellen

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2022-0302Xerox FreeFlow Print Server: Mehrere Schwachstellen ermöglichen Ausführen von beliebigem Programmcode mit Administratorrechten

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um beliebigen Programmcode auszuführen, einen Cross-Site-Scripting-Angriff durchzuführen, Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder Dateien zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2023-1350Splunk Splunk Enterprise: Mehrere Schwachstellen in Komponenten von Drittanbietern

Ein Angreifer kann mehrere Schwachstellen in Splunk Splunk Enterprise in diversen Komponenten von Drittanbietern ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2022-2354cURL + libcurl: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein Angreifer kann eine Schwachstelle in cURL und libcurl unter macOS ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20210811Security Bulletin 11 Aug 2021

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 11 Aug 2021, published on 11 August 2021. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

d?id=CVE-2021-20266 Référence CVE CVE-2021-20284 https://www.cve.org/CVERecord?id=CVE-2021-20284 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=CVE-2021-22945 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-27645 https://www.cve.org/CVERecord?id=CVE-2021-27645 Référence CVE CVE-2021-29390 https://www.cve.org/CVERecord?id=CVE-2021-29390 Référence CVE CVE-2021-30560 https://www.cve.org/CVERecord?id=CVE-2021-30560 Référence CVE CVE-2021-32256 https://www.cve.org/CVERecord?id=CVE-2021-32256 Référence CVE CVE-2021-32292 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0199Multiples vulnérabilités dans les produits VMware

VERecord?id=CVE-2020-8169 Référence CVE CVE-2020-8177 https://www.cve.org/CVERecord?id=CVE-2020-8177 Référence CVE CVE-2020-8284 https://www.cve.org/CVERecord?id=CVE-2020-8284 Référence CVE CVE-2020-8908 https://www.cve.org/CVERecord?id=CVE-2020-8908 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-23840 https://www.cve.org/CVERecord?id=CVE-2021-23840 Référence CVE CVE-2021-23841 https://www.cve.org/CVERecord?id=CVE-2021-23841 Référence CVE CVE-2021-3449 https://www.cve.org/CVERecord?id=CVE-2021-3449 Référence CVE CVE-2021-3711 https://www.cve.org/CVERecord?id=CVE-2021-3711 Référence CVE CVE-2021-3712 https://www.cve.org/CVERecord?id=CVE-2021-3712 Référence CVE CVE-2021-37600 https://www.cve.org/CVERecord?id=CVE-20

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0145Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2020-24553 Référence CVE CVE-2020-28362 https://www.cve.org/CVERecord?id=CVE-2020-28362 Référence CVE CVE-2020-28366 https://www.cve.org/CVERecord?id=CVE-2020-28366 Référence CVE CVE-2020-28367 https://www.cve.org/CVERecord?id=CVE-2020-28367 Référence CVE CVE-2020-29510 https://www.cve.org/CVERecord?id=CVE-2020-29510 Référence CVE CVE-2020-8244 https://www.cve.org/CVERecord?id=CVE-2020-8244 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-27918 https://www.cve.org/CVERecord?id=CVE-2021-27918 Référence CVE CVE-2021-29923 https://www.cve.org/CVERecord?id=CVE-2021-29923 Référence CVE CVE-2021-3114 https://www.cve.org/CVERecord?id=CVE-2021-3114 Référence CVE CVE-2021-31525 https://www.cve.org/CVERecord?id=CVE-2021-31525 Référence CVE CVE-2021-33194 https://www.cve.org/CVERecord?id=CVE-2021-33194 Référence CVE CVE-2021-33195 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-1015Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2021-22876 Référence CVE CVE-2021-22890 https://www.cve.org/CVERecord?id=CVE-2021-22890 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=CVE-2021-22945 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-23336 https://www.cve.org/CVERecord?id=CVE-2021-23336 Référence CVE CVE-2021-27212 https://www.cve.org/CVERecord?id=CVE-2021-27212 Référence CVE CVE-2021-27218 https://www.cve.org/CVERecord?id=CVE-2021-27218 Référence CVE CVE-2021-27219 https://www.cve.org/CVERecord?id=CVE-2021-27219 Référence CVE CVE-2021-27645 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0701Multiples vulnérabilités dans Splunk

d?id=CVE-2021-22876 Référence CVE CVE-2021-22890 https://www.cve.org/CVERecord?id=CVE-2021-22890 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=CVE-2021-22945 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-23343 https://www.cve.org/CVERecord?id=CVE-2021-23343 Référence CVE CVE-2021-23382 https://www.cve.org/CVERecord?id=CVE-2021-23382 Référence CVE CVE-2021-27918 https://www.cve.org/CVERecord?id=CVE-2021-27918 Référence CVE CVE-2021-27919 https://www.cve.org/CVERecord?id=CVE-2021-27919 Référence CVE CVE-2021-29060 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0428Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2021-22876 Référence CVE CVE-2021-22890 https://www.cve.org/CVERecord?id=CVE-2021-22890 Référence CVE CVE-2021-22897 https://www.cve.org/CVERecord?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=CVE-2021-22945 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-23343 https://www.cve.org/CVERecord?id=CVE-2021-23343 Référence CVE CVE-2021-23368 https://www.cve.org/CVERecord?id=CVE-2021-23368 Référence CVE CVE-2021-23382 https://www.cve.org/CVERecord?id=CVE-2021-23382 Référence CVE CVE-2021-27292 https://www.cve.org/CVERecord?id=CVE-2021-27292 Référence CVE CVE-2021-29060 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-487Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service et un contournement de la politique de sécurité.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-216Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2021-22897 Référence CVE CVE-2021-22898 https://www.cve.org/CVERecord?id=CVE-2021-22898 Référence CVE CVE-2021-22901 https://www.cve.org/CVERecord?id=CVE-2021-22901 Référence CVE CVE-2021-22918 https://www.cve.org/CVERecord?id=CVE-2021-22918 Référence CVE CVE-2021-22921 https://www.cve.org/CVERecord?id=CVE-2021-22921 Référence CVE CVE-2021-22922 https://www.cve.org/CVERecord?id=CVE-2021-22922 Référence CVE CVE-2021-22923 https://www.cve.org/CVERecord?id=CVE-2021-22923 Référence CVE CVE-2021-22924 https://www.cve.org/CVERecord?id=CVE-2021-22924 Référence CVE CVE-2021-22925 https://www.cve.org/CVERecord?id=CVE-2021-22925 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22930 https://www.cve.org/CVERecord?id=CVE-2021-22930 Référence CVE CVE-2021-22931 https://www.cve.org/CVERecord?id=CVE-2021-22931 Référence CVE CVE-2021-22939 https://www.cve.org/CVERecord?id=CVE-2021-22939 Référence CVE CVE-2021-22940 https://www.cve.org/CVERecord?id=CVE-2021-22940 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=CVE-2021-22945 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-23362 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2021-AVI-801Multiples vulnérabilités dans Oracle MySQL

s permettent à un attaquant de provoquer une exécution de code arbitraire, un déni de service à distance et une atteinte à l'intégrité des données. Solution Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation). Documentation Bulletin de sécurité Oracle cpuoct2021 du 19 octobre 2021 https://www.oracle.com/security-alerts/cpuoct2021verbose.html#MSQL Référence CVE CVE-2021-20227 https://www.cve.org/CVERecord?id=CVE-2021-20227 Référence CVE CVE-2021-22112 https://www.cve.org/CVERecord?id=CVE-2021-22112 Référence CVE CVE-2021-22118 https://www.cve.org/CVERecord?id=CVE-2021-22118 Référence CVE CVE-2021-22926 https://www.cve.org/CVERecord?id=CVE-2021-22926 Référence CVE CVE-2021-22931 https://www.cve.org/CVERecord?id=CVE-2021-22931 Référence CVE CVE-2021-2471 https://www.cve.org/CVERecord?id=CVE-2021-2471 Référence CVE CVE-2021-2478 https://www.cve.org/CVERecord?id=CVE-2021-2478 Référence CVE CVE-2021-2479 https://www.cve.org/CVERecord?id=CVE-2021-2479 Référence CVE CVE-2021-2481 https://www.cve.org/CVERecord?id=CVE-2021-2481 Référence CVE CVE-2021-29425 https://www.cve.org/CVERecord?id=CVE-2021-29425 Référence CVE CVE-2021-33037 https://www.cve.org/CVERecord?id=CVE-2021-33037 Référence CVE CVE-2021-3518 https://www.cve.org/CVERecord?id=CVE-2021-

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-009764cURL における証明書検証に関する脆弱性

cURL には、証明書検証に関する脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
https://github.com/curl/curl: curll 7.33.0 to and include 7.77.0
Fixed
Update to V3.1.5 or later version
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 5 Aug 2021 · Last source change 28 May 2026, 19:49 UTC · CWE-840

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-10055
Product sourceCNA
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD modified after enrichment

Missing structured fields: affected product. Missing data is not evidence of low risk; review the primary advisory.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    curll 7.33.0 to and include 7.77.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    curll 7.33.0 to and include 7.77.0 · Fixed: Update to V3.1.5 or later version
    Siemens ProductCERT ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: sick.com/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf; removed remediation: sick.com/psirt.
    Before
    remediation: sick.com/psirt
    After
    remediation: sick.com/special_information_sick_operating_guidelines_cybersecurity_by_sick_en_im0106719.pdf
    SICK PSIRT ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2021-10055↗Vendor CSAF · SUSE Product Security Team↗Siemens ProductCERT security advisory · Siemens SSA-398330↗CISA Vulnrichment SSVC evidence↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Public exploit reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2021-22926 · cve.blacktree.nl