How severe is GHSA-r3hf-q3mf-7h6w?

GHSA-r3hf-q3mf-7h6w has a CVSS score of 3.7/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-r3hf-q3mf-7h6w?

GHSA-r3hf-q3mf-7h6w affects the following packages: hybridauth/hybridauth (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-r3hf-q3mf-7h6w?

No patched version of hybridauth/hybridauth has shipped for GHSA-r3hf-q3mf-7h6w yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-r3hf-q3mf-7h6w in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hybridauth/hybridauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-r3hf-q3mf-7h6w 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 GHSA-r3hf-q3mf-7h6w actively exploited in the wild?

No public exploit code has been indexed for GHSA-r3hf-q3mf-7h6w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-r3hf-q3mf-7h6w?

GHSA-r3hf-q3mf-7h6w has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 16th 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.

When was GHSA-r3hf-q3mf-7h6w published, and has it been updated?

GHSA-r3hf-q3mf-7h6w was published on March 23, 2026 and was last updated on March 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

LOW severity

GHSA-r3hf-q3mf-7h6w — hybridauth/hybridauth

LOW

GHSA-r3hf-q3mf-7h6w is a low-severity (CVSS 3.7) vulnerability in hybridauth/hybridauth. No vendor fix is recorded yet; mitigation options are listed below.

HybridAuth Has Improper SSL Certificate Validation in Curl HTTP Client

Also known asCVE-2026-4587

Published

Mar 23, 2026

Updated

Mar 27, 2026

Affected

1 pkg

Patched

None yet

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, 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 GHSA-r3hf-q3mf-7h6w.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-r3hf-q3mf-7h6w by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

🐘hybridauth/hybridauth

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

A vulnerability was found in HybridAuth up to 3.12.2. This issue affects some unknown processing of the file src/HttpClient/Curl.php of the component SSL Handler. The manipulation of the argument curlOptions results in improper certificate validation. The attack can be launched remotely. This attack is characterized by high complexity. The exploitability is assessed as difficult. The project was informed of the problem early through an issue report but has not responded yet.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`hybridauth/hybridauth`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for hybridauth/hybridauth, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of hybridauth/hybridauth has shipped for GHSA-r3hf-q3mf-7h6w yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-r3hf-q3mf-7h6w in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works