Skip to content
Noroxi
NVD / CVE Program· CNA hackerone

CVE-2022-32221: When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when th

Noroxi assessment

Priority: Plan (action score 41/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 5% (FIRST EPSS); higher than 92.4% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: curl (AlmaLinux:9) 7.76.1-19.el9_1.1; curl-minimal (AlmaLinux:9) 7.76.1-19.el9_1.1; libcurl (AlmaLinux:9) 7.76.1-19.el9_1.1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Add it to your regular patch cycle. Upgrade to curl (AlmaLinux:9) 7.76.1-19.el9_1.1; curl-minimal (AlmaLinux:9) 7.76.1-19.el9_1.1; libcurl (AlmaLinux:9) 7.76.1-19.el9_1.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent `POST` request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Dec 5, 2022
Updated
Oct 14, 2026
EPSS
5.0% · 92th percentile

Report tools

JSON

Action score

41

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
2 / 30 · 5.0%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
9.8
CNA · hackerone
9.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2022-32221

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
haxxcurl
netappclustered data ontap
netapph300s firmware
netapph300s
netapph500s firmware
netapph500s
netapph700s firmware
netapph700s
netapph410s firmware
netapph410s
debiandebian linux
applemacos

and 1 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apple macosbefore 12.6.3
  • debian debian linux10.0
  • debian debian linux11.0
  • haxx curlbefore 7.86.0
  • netapp clustered data ontapall versions
  • netapp h300s firmwareall versions
  • netapp h410s firmwareall versions
  • netapp h500s firmwareall versions
  • netapp h700s firmwareall versions
  • splunk universal forwarder8.2.0 and later · before 8.2.12
  • splunk universal forwarder9.0.0 and later · before 9.0.6
  • splunk universal forwarder9.1.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (hackerone). Independent of NVD's CPE analysis and usually ahead of it.

  • n/a https://github.com/curl/curl

    • Fixed in 7.86.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9curlbefore 7.76.1-19.el9_1.17.76.1-19.el9_1.1
AlmaLinux:9curl-minimalbefore 7.76.1-19.el9_1.17.76.1-19.el9_1.1
AlmaLinux:9libcurlbefore 7.76.1-19.el9_1.17.76.1-19.el9_1.1
AlmaLinux:9libcurl-develbefore 7.76.1-19.el9_1.17.76.1-19.el9_1.1
AlmaLinux:9libcurl-minimalbefore 7.76.1-19.el9_1.17.76.1-19.el9_1.1
Alpine:v3.15curlbefore 7.80.0-r47.80.0-r4
Alpine:v3.16curlbefore 7.83.1-r47.83.1-r4
Alpine:v3.17curlbefore 7.86.0-r07.86.0-r0
Debian:10curlbefore 7.64.0-4+deb10u47.64.0-4+deb10u4
Debian:11curlbefore 7.74.0-1.3+deb11u57.74.0-1.3+deb11u5
Debian:12curlbefore 7.86.0-17.86.0-1
openSUSE:Leap 15.4curlbefore 7.79.1-150400.5.9.17.79.1-150400.5.9.1
openSUSE:Leap Micro 5.2curlbefore 7.66.0-150200.4.42.17.66.0-150200.4.42.1
openSUSE:Tumbleweedcurlbefore 7.86.0-1.17.86.0-1.1
Red Hat:enterprise_linux:9::appstreamcurl-debuginfobefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1
Red Hat:enterprise_linux:9::appstreamcurl-debugsourcebefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1
Red Hat:enterprise_linux:9::appstreamcurl-minimal-debuginfobefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1
Red Hat:enterprise_linux:9::appstreamlibcurl-debuginfobefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1
Red Hat:enterprise_linux:9::appstreamlibcurl-develbefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1
Red Hat:enterprise_linux:9::appstreamlibcurl-minimal-debuginfobefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1
Red Hat:enterprise_linux:9::baseoscurlbefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1
Red Hat:enterprise_linux:9::baseoscurl-minimalbefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1
Red Hat:enterprise_linux:9::baseoslibcurlbefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1
Red Hat:enterprise_linux:9::baseoslibcurl-minimalbefore 0:7.76.1-19.el9_1.10:7.76.1-19.el9_1.1

+68

Same product

haxx: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session t
    51Plan
  • CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
    47Plan
  • CVE-2024-2398HTTP/2 push headers memory-leak
    45Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-42916Oct 29, 2022 · In curl before 7.86.0, the HSTS check could be bypassed to trick it into staying with HTTP.
    31Monitor
  • ← EarlierCVE-2022-42915Oct 29, 2022 · curl before 7.86.0 has a double free.
    33Monitor
  • Later →CVE-2022-35260Dec 5, 2022 · curl can be told to parse a `.netrc` file for credentials.
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
almalinux:curl7.76.1-19.el9_1.1 · AlmaLinux:9Package registry (OSV)
almalinux:curl-minimal7.76.1-19.el9_1.1 · AlmaLinux:9Package registry (OSV)
almalinux:libcurl7.76.1-19.el9_1.1 · AlmaLinux:9Package registry (OSV)
almalinux:libcurl-devel7.76.1-19.el9_1.1 · AlmaLinux:9Package registry (OSV)
almalinux:libcurl-minimal7.76.1-19.el9_1.1 · AlmaLinux:9Package registry (OSV)
alpine:curl7.80.0-r4 · Alpine:v3.15Package registry (OSV)
debian:curl7.86.0-1 · Debian:12Package registry (OSV)
opensuse:curl7.66.0-150200.4.42.1 · openSUSE:Leap Micro 5.2Package registry (OSV)
red hat:jbcs-httpd24-httpd0:2.4.51-37.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-httpd-debuginfo0:2.4.51-37.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-httpd-devel0:2.4.51-37.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-httpd-manual0:2.4.51-37.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-httpd-selinux0:2.4.51-37.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-openssl1:1.1.1k-13.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-openssl-debuginfo1:1.1.1k-13.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-openssl-devel1:1.1.1k-13.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-openssl-libs1:1.1.1k-13.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-openssl-libs-debuginfo1:1.1.1k-13.el8jbcs · Red Hat:jboss_core_services:1::el8Package registry (OSV)
red hat:jbcs-httpd24-openssl-perl1:1.1.1k-13.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
red hat:jbcs-httpd24-openssl-static1:1.1.1k-13.el7jbcs · Red Hat:jboss_core_services:1::el7Package registry (OSV)
rocky linux:curl0:7.76.1-19.el9_1.1 · Rocky Linux:9Package registry (OSV)
suse:curl7.60.0-11.49.1 · SUSE:Linux Enterprise Software Development Kit 12 SP5Package registry (OSV)
suse:curl7.66.0-150200.4.42.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records