CVE-2022-43551
HIGHEPSS 97th pctlDescription
A vulnerability exists in curl <7.87.0 HSTS check that could be bypassed to trick it to keep using HTTP. Using its HSTS support, curl can be instructed to use HTTPS instead of using an insecure clear-text HTTP step even when HTTP is provided in the URL. However, the HSTS mechanism could be bypassed if the host name in the given URL first uses IDN characters that get replaced to ASCII counterparts as part of the IDN conversion. Like using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop (U+002E) `.`. Then in a subsequent request, it does not detect the HSTS state and makes a clear text transfer. Because it would store the info IDN encoded but look for it IDN decoded.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Very high risk: more likely to be exploited than 97% of all known CVEs.
References
Related Vulnerabilities
Other CWE-319 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2018-12710 | High | 8.0 | 77% | - | - |
| CVE-2024-25735 | Critical | 9.1 | 51% | - | Fix |
| CVE-2019-3993 | High | 7.5 | 46% | - | - |
| CVE-2017-5259 | High | 8.8 | 39% | - | - |
| CVE-2016-5649 | Critical | 9.8 | 27% | - | - |
| CVE-2021-39341 | High | 8.2 | 22% | - | - |
Common questions
How do I fix CVE-2022-43551?
Published advisories record a fix for 126 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2022-43551 being actively exploited?
Not that we know of. CVE-2022-43551 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 16.5% is the estimated probability that it will be exploited in the next 30 days. That is higher than 97% of all scored CVEs.
How severe is CVE-2022-43551?
CVE-2022-43551 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2022-43551 affect?
Published advisories record a fix for curl (Debian), jbcs-httpd24-apr-util (Rocky), jbcs-httpd24-apr-util (Red Hat / RHEL), jbcs-httpd24-apr-util-debuginfo (Red Hat / RHEL), and 122 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2022-43551
Markdown
[](https://tridentstack.com/cve/CVE-2022-43551)HTML
<a href="https://tridentstack.com/cve/CVE-2022-43551"><img src="https://tridentstack.com/cve/badge/CVE-2022-43551.svg" alt="CVE-2022-43551"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-02-13.