{"id":"CVE-2021-22926","aliases":["ALPINE-CVE-2021-22926","AZL-6364","CURL-CVE-2021-22926","EUVD-2021-10055","GHSA-5xph-62q2-pxff","JLSEC-2026-1338","OESA-2021-1321","openSUSE-SU-2024:12116-1"],"status":"published","title":"libcurl-using applications can ask for a specific client certificate to be used in a transfer....","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.","severity":{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-11","score":0.1514,"percentile":0.96783,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-295","CWE-840"],"published":"2021-07-21T08:00:00Z","modified":"2026-10-25T01:04:48Z","fixes":[{"ecosystem":"Alpine:v3.11","package":"curl","fixed_in":["7.67.0-r5"],"sources":["osv"]},{"ecosystem":"Azure Linux:2","package":"curl","fixed_in":["7.82.0-1"],"sources":["osv"]},{"ecosystem":"Julia","package":"LibCURL_jll","fixed_in":["7.81.0+0"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.11","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.33.0"},{"fixed":"7.67.0-r5"}]}]},{"source":"osv","ecosystem":"Azure Linux:2","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.82.0-1"}]}]},{"source":"osv","ecosystem":"Julia","package":"LibCURL_jll","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.81.0+0"}]}]},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP1","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.71.1-10.oe1"}]}],"bundled":2},{"source":"osv","ecosystem":"openEuler:20.03-LTS-SP2","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.71.1-10.oe1"}]}],"bundled":2}],"products":[{"vendor":"haxx","product":"curl"},{"vendor":"netapp","product":"active_iq_unified_manager"},{"vendor":"netapp","product":"clustered_data_ontap"},{"vendor":"netapp","product":"h300e_firmware"},{"vendor":"netapp","product":"h300s_firmware"},{"vendor":"netapp","product":"h410s_firmware"},{"vendor":"netapp","product":"h500e_firmware"},{"vendor":"netapp","product":"h500s_firmware"},{"vendor":"netapp","product":"h700e_firmware"},{"vendor":"netapp","product":"h700s_firmware"},{"vendor":"netapp","product":"hci_management_node"},{"vendor":"netapp","product":"oncommand_insight"},{"vendor":"netapp","product":"oncommand_workflow_automation"},{"vendor":"netapp","product":"snapcenter"},{"vendor":"netapp","product":"solidfire"},{"vendor":"oracle","product":"mysql_server"},{"vendor":"oracle","product":"peoplesoft_enterprise_peopletools"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518-4 pn/dp mfp"},{"vendor":"siemens","product":"simatic s7-1500 cpu 1518f-4 pn/dp mfp"},{"vendor":"siemens","product":"sinec_infrastructure_network_services"},{"vendor":"siemens","product":"siplus s7-1500 cpu 1518-4 pn/dp mfp"},{"vendor":"splunk","product":"universal_forwarder"}],"references":[{"url":"https://hackerone.com/reports/1234760","tags":["x_transferred","Exploit","Third Party Advisory","evidence","web"]},{"url":"https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc%40%3Cdev.kafka.apache.org%3E","tags":["mailing-list","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc%40%3Cusers.kafka.apache.org%3E","tags":["mailing-list","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7%40%3Cusers.kafka.apache.org%3E","tags":["mailing-list","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7%40%3Cdev.kafka.apache.org%3E","tags":["mailing-list","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://www.oracle.com/security-alerts/cpuoct2021.html","tags":["x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"https://security.netapp.com/advisory/ntap-20210902-0003/","tags":["x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://www.oracle.com/security-alerts/cpujan2022.html","tags":["x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"https://security.netapp.com/advisory/ntap-20211022-0003/","tags":["x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://cert-portal.siemens.com/productcert/pdf/ssa-389290.pdf","tags":["x_transferred","Patch","Third Party Advisory","fix","web"]},{"url":"https://security.gentoo.org/glsa/202212-01","tags":["vendor-advisory","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-389290.html","tags":["web"]},{"url":"https://cert-portal.siemens.com/productcert/html/ssa-398330.html","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-22926","tags":["web","advisory"]},{"url":"https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc@%3Cdev.kafka.apache.org%3E"},{"url":"https://lists.apache.org/thread.html/r61db8e7dcb56dc000a5387a88f7a473bacec5ee01b9ff3f55308aacc@%3Cusers.kafka.apache.org%3E"},{"url":"https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7@%3Cdev.kafka.apache.org%3E"},{"url":"https://lists.apache.org/thread.html/rbf4ce74b0d1fa9810dec50ba3ace0caeea677af7c27a97111c06ccb7@%3Cusers.kafka.apache.org%3E"},{"url":"https://security.netapp.com/advisory/ntap-20210902-0003"},{"url":"https://security.netapp.com/advisory/ntap-20211022-0003"},{"url":"https://github.com/advisories/GHSA-5xph-62q2-pxff"},{"url":"https://security.alpinelinux.org/vuln/CVE-2021-22926","tags":["advisory"]},{"url":"https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1321","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2021-22925","tags":["advisory"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2020-10531","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15190","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15191","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15194","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-15209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26266","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-26270","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22923","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22926","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37635","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37636","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37637","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37638","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37639","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37640","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37641","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37642","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37643","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37644","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37645","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37646","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37647","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37648","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37649","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37650","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37651","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37652","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37653","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37654","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37655","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37656","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37657","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37658","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37659","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37660","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37661","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37662","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37663","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37664","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37665","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37666","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37667","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37668","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37669","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37670","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37671","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37672","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37673","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37674","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37675","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37676","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37677","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37678","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37679","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37680","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37681","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37682","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37683","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37684","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37685","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37686","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37687","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37688","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37690","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37691","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-37692","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41195","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41196","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41197","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41198","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41199","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41200","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41201","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41202","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41203","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41204","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41205","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41206","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41207","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41208","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41209","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41210","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41211","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41212","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41213","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41214","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41215","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41216","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41217","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41218","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41219","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41220","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41221","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41222","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41223","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41224","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41225","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41226","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41227","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-41228","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21726","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21727","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21728","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21729","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21730","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21731","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21732","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21733","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21734","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21735","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21736","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21737","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21738","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21739","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21740","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-21741","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23557","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23558","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23559","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23560","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23561","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23562","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23563","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23564","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23565","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23566","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23567","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23568","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23569","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23570","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23571","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23572","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23573","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23574","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23575","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23576","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23577","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23578","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23579","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23580","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23581","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23582","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23583","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23584","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23585","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23587","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23588","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23589","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23590","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23591","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2022-23595","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2021-22926","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.","status":"published","published":"2021-08-05T00:00:00Z","modified":"2026-10-14T11:13:52.289Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"adp"}],"cwes":["CWE-840"],"updated_at":"2026-11-02T14:32:57.701381Z"}],"euvd":[{"id":"EUVD-2021-10055","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.","status":"published","published":"2021-08-05T00:00:00Z","modified":"2026-10-14T11:13:52Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T17:27:16.356399Z"}],"ghsa":[{"id":"GHSA-5xph-62q2-pxff","title":"libcurl-using applications can ask for a specific client certificate to be used in a transfer....","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.","status":"published","published":"2022-05-24T19:10:06Z","modified":"2026-10-14T12:32:27Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T15:13:24.812204Z"}],"nvd":[{"id":"CVE-2021-22926","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.","status":"published","published":"2021-08-05T21:15:11.553Z","modified":"2026-10-14T12:17:07.373Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"secondary"},{"version":"2.0","score":5,"vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-840","CWE-295"],"updated_at":"2026-11-02T14:06:56.562207Z"}],"osv":[{"id":"ALPINE-CVE-2021-22926","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.","status":"published","published":"2021-08-05T21:15:11.553Z","modified":"2026-10-23T17:17:56.153349278Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:27:48.646074Z"},{"id":"AZL-6364","title":"CVE-2021-22926 affecting package curl for versions less than 7.82.0-1","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.","status":"published","published":"2021-08-05T21:15:11Z","modified":"2026-04-21T04:32:11.039053Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:07.805289Z"},{"id":"CVE-2021-22926","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.","status":"published","published":"2021-08-05T21:15:11.553Z","modified":"2026-10-24T10:30:38.896190535Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:18.367807Z"},{"id":"JLSEC-2026-1338","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.","status":"published","published":"2026-08-17T13:15:13.4Z","modified":"2026-08-17T13:30:03.148441908Z","cvss":[{"version":"2.0","score":5,"vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","level":"medium"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:47:18.159338Z"},{"id":"OESA-2021-1321","title":"curl security update","description":"cURL is a computer software project providing a library (libcurl) and command-line tool (curl) for transferring data using various protocols.\r\n\r\nSecurity Fix(es):\r\n\r\ncurl supports the `-t` command line option, known as `CURLOPT_TELNETOPTIONS`in libcurl. This rarely used option is used to send variable=content pairs toTELNET servers.Due to flaw in the option parser for sending `NEW_ENV` variables, libcurlcould be made to pass on uninitialized data from a stack based buffer to theserver. Therefore potentially revealing sensitive internal information to theserver using a clear-text network protocol.This could happen because curl did not call and use sscanf() correctly whenparsing the string provided by the application.(CVE-2021-22925)\r\n\r\nlibcurl-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.(CVE-2021-22926)","status":"published","published":"2021-08-20T11:04:33Z","modified":"2026-08-18T01:15:51.801658975Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T15:52:38.987987Z"},{"id":"CURL-CVE-2021-22926","title":"CURLOPT_SSLCERT mix-up with Secure Transport","description":"libcurl-using applications can ask for a specific client certificate to be\nused in a transfer. This is done with the `CURLOPT_SSLCERT` option (`--cert`\nwith the command line tool).\n\nWhen libcurl is built to use the macOS native TLS library Secure Transport, an\napplication can ask for the client certificate by name or with a filename -\nusing the same option. If the name exists as a file, it is used instead of by\nname.\n\nIf the application runs with a current working directory that is writable by\nother users (like `/tmp`), a malicious user can create a filename with the\nsame name as the app wants to use by name, and thereby trick the application\nto use the file based cert instead of the one referred to by name making\nlibcurl send the wrong client certificate in the TLS connection handshake.","status":"published","published":"2021-07-21T08:00:00Z","modified":"2026-10-25T01:04:48.497389824Z","updated_at":"2026-11-02T15:43:55.669514Z"},{"id":"openSUSE-SU-2024:12116-1","title":"tensorflow-lite-2.9.1-1.1 on GA media","description":"These are all security issues fixed in the tensorflow-lite-2.9.1-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T03:04:19.609756Z","updated_at":"2026-11-02T16:58:35.485255Z"}]}}