How severe is CVE-2022-27776?

No CVSS score has been assigned to CVE-2022-27776 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2022-27776?

Affected package information for CVE-2022-27776 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-27776?

Upgrade the affected component to the fixed release for CVE-2022-27776, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.

How do I detect CVE-2022-27776 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2022-27776 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-27776 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-27776, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-27776?

CVE-2022-27776 has an EPSS (Exploit Prediction Scoring System) score of 4.1%, placing it in the 91th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-27776?

CVE-2022-27776 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-27776 published, and has it been updated?

CVE-2022-27776 was published on June 1, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2022-27776 — curl

CVE-2022-27776 is a CWE-522 vulnerability. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available — see the affected versions and patch details below.

Also known asCURL-CVE-2022-27776

Published

Jun 1, 2022

Updated

Oct 28, 2026

Affected

13 products

Patched

See advisory

Exploits

1 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-27776.

EPSS Exploitation Probability

via FIRST.org ↗

4.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.

Affected Products

13 products · 17 configurations

fabric operating systembroadcom

all

debian linuxdebian

2 versions

10.011.0

fedorafedoraproject

2 versions

3637

Application

curlhaxx

< 7.83.0

range

Application

clustered data ontapnetapp

all

h300s firmwarenetapp

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A insufficiently protected credentials vulnerability in fixed in curl 7.…

hackerone.comNVDJun 2022

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Fix
Upgrade the affected component to the fixed release for CVE-2022-27776, or apply your distribution's backported patch — distro builds are often patched at an older version number, so check your vendor's advisory rather than the upstream version alone.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 8	`curl-0:7.61.1-22.el8_6.3`	RHSA-2022:5313
Red Hat Enterprise Linux 9	`curl-0:7.76.1-14.el9_0.4`	RHSA-2022:5245

Frequently Asked Questions

A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number.

O3 Security · Impact-Aware SCA

Is CVE-2022-27776 in your dependencies?

Find it across your dependency tree, including transitive dependencies.

Scan my dependencies How O3 SCA works