ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2022-42916

In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP.

Published Oct 29, 2022 · catalog updated Oct 14, 2026 · In curl before 7.86.0,

Check if you run it

No confirmed exploitation is on record for CVE-2022-42916. EPSS is 2.01%. Act only if a listed version of In curl before 7.86.0, is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (In curl before 7.86.0,).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
2.01%
Remediation
Advisory link
Affected products
cpe apple/macos · cpe fedoraproject/fedora · cpe haxx/curl · cpe splunk/universal forwarder

In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN conversion, e.g., using the character UTF-8 U+3002 (IDEOGRAPHIC FULL STOP) instead of the common ASCII full stop of U+002E (.). The earliest affected version is 7.77.0 2021-05-26.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe apple/macosversion unspecified
  • cpe fedoraproject/fedora35
  • cpe fedoraproject/fedora36
  • cpe fedoraproject/fedora37
  • cpe haxx/curlversion unspecified
  • cpe splunk/universal forwarderversion unspecified

How to fix CVE-2022-42916

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2022-42916. EPSS is 2.01%. Act only if a listed version of In curl before 7.86.0, is installed.

Which versions are affected?

Compare what you have installed with 35, 36, 37. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-319: Cleartext Transmission of Sensitive Information. EPSS 2.01%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 29, 2022 · NIST NVD

    Detected

    In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN c

  2. Oct 14, 2026 · NIST NVD

    Updated

    In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypassed if the host name in the given URL uses IDN characters that get replaced with ASCII counterparts as part of the IDN c

Sources

  • CVE.orgVulnerability recordCVE-2022-42916

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2022-42916

    30-day exploitation probability 2.0%

    first.org
  • NIST NVDVulnerability recordCVE-2022-42916

    In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP. Using its HSTS support, curl can be instructed to use HTTPS directly (instead of using an insecure cleartext HTTP step) even when HTTP is provided in the URL. This mechanism could be bypas

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 16, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.