# CVE-2022-27779: Other in https://github.com/curl/curl

> Attackers can set cookies for top-level domains via trailing dots, allowing cookie theft or session hijacking across unrelated sites.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jun 2022
- **Updated:** 14 Oct 2026
- **Also known as:** ALPINE-CVE-2022-27779, AZL-9908, CLEANSTART-2026-UF88826, CURL-CVE-2022-27779, DEBIAN-CVE-2022-27779, GHSA-r5c3-3mf2-x8c7

## What is CVE-2022-27779?

CVE-2022-27779 is a medium-severity vulnerability in Haxx Curl, published on 1 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

libcurl wrongly allows cookies to be set for Top Level Domains (TLDs) if thehost name is provided with a trailing dot.curl can be told to receive and send cookies. curl's "cookie engine" can bebuilt with or without [Public Suffix List](https://publicsuffix.org/)awareness. If PSL support not provided, a more rudimentary check exists to atleast prevent cookies from being set on TLDs. This check was broken if thehost name in the URL uses a trailing dot.This can allow arbitrary sites to set cookies that then would get sent to adifferent and unrelated site or domain.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2022-27779?

It affects 11 products.


Products: Haxx Curl, Netapp Clustered Data Ontap, Netapp H300s Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware, Netapp Hci Bootstrap Os, Netapp Hci Compute Node, Netapp Solidfire\, Enterprise Sds \& Hci Storage Node, Netapp Solidfire \& Hci Management Node, Splunk Universal Forwarder.

## How do I fix CVE-2022-27779?

Upgrade to a fixed version.

## Is CVE-2022-27779 being exploited?

There is no known exploitation of CVE-2022-27779 in the wild and no public exploit code.

## Other vulnerabilities in Haxx Curl

- [CVE-2026-19931](https://insights.sbomify.com/CVE-2026-19931/): Negotiate ambient user conn reuse (critical 9.8)
- [CVE-2026-10536](https://insights.sbomify.com/CVE-2026-10536/): HTTP/2 stream-dependency tree UAF (critical 9.8)
- [CVE-2026-11856](https://insights.sbomify.com/CVE-2026-11856/): cross-origin Digest auth state leak (critical 9.8)
- [CVE-2026-8925](https://insights.sbomify.com/CVE-2026-8925/): SASL double-free (critical 9.8)
- [CVE-2026-9079](https://insights.sbomify.com/CVE-2026-9079/): stale proxy password leak (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27779 and fix it if it is affected.

What it is: CVE-2022-27779 is a medium-severity vulnerability in Haxx Curl, published on 1 Jun 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-27779 in the wild and no public exploit code.

Affected product: Haxx Curl. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-27779/ (Markdown: https://insights.sbomify.com/CVE-2022-27779/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-27779
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-27779
- OSV: https://osv.dev/vulnerability/CVE-2022-27779

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-27779/
Summaries are generated and may contain mistakes; the official description above is the record.