CVE Intelligence
Medium Authentication exploit reference

CVE-2022-27774 — An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82...

An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers.

Published Jun 2, 2022 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: hackerone

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 1.9% (30-day exploitation probability)+12
  • Technical severity (medium)+3
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
1.87%
ahead of 79% of scored CVEs · Oct 14, 2026
Affects
Broadcom
Fabric Operating System and 11 more
CVSS base
5.7
Medium · 4 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Broadcom Fabric Operating System, Debian Debian Linux, Haxx Curl…).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (authentication), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Broadcom Fabric Operating System versions not specified by the source Vulnerable NIST National Vulnerability Database
Debian Debian Linux version 10.0version 11.0 Vulnerable NIST National Vulnerability Database
Haxx Curl ≥ 4.9 and ≤ 7.82.0 Vulnerable NIST National Vulnerability Database
Netapp Clustered Data Ontap versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H300s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H410s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H500s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp H700s Firmware versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Hci Bootstrap Os versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Solidfire & Hci Management Node versions not specified by the source Vulnerable NIST National Vulnerability Database
Netapp Solidfire & Hci Storage Node versions not specified by the source Vulnerable NIST National Vulnerability Database
Splunk Universal Forwarder ≥ 8.2.0 and < 8.2.12≥ 9.0.0 and < 9.0.6version 9.1.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
5.7 CVSS 3.1 Medium 2.1 3.6 nvd@nist.gov via NIST National Vulnerability Database
5.7 CVSS 3.1 Medium 2.1 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
5.7 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
5.7 CVSS 3.1 Medium — — CISA-ADP via CVE Program (cve.org) e CISA ADP
3.5 CVSS 2.0 Low 6.8 2.9 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-522 · Insufficiently Protected Credentials

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.87%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Review authentication logs: logins without MFA, anomalous sessions and recently created accounts.
web/proxy/WAF logsnetwork IDS/IPSauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 5.7
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2022
  • CVE published
    Jun 2, 2022 · hackerone

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

9 on the record

Elsewhere on this site

Broadcom
every CVE for this vendor
Authentication
same class
CWE-522
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-94587 A buffer overflow vulnerability exists in the WebTools administrative interface handling... 7d
  • High CVE-2026-94577 A privilege escalation vulnerability exists in the internal Command-Line Interface (CLI)... 7d
  • High CVE-2026-94579 An OS command injection vulnerability exists in the PAM (Pluggable Authentication Module) session... 7d
  • Medium CVE-2026-94581 An OS command injection vulnerability exists in the REST API management interface of Brocade... 7d
  • Medium CVE-2026-94586 A command injection vulnerability exists in the WebTools administrative interface handling... 7d
  • High CVE-2026-94585 An authentication bypass vulnerability exists in the web management interface of Brocade Fabric... 7d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-27774 is "An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82...", rated Medium. It affects Fabric Operating System (Broadcom); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.7 describes technical severity. EPSS 1.87% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.