How severe is GHSA-gcfg-hmwx-wq5h?

GHSA-gcfg-hmwx-wq5h has a CVSS score of 7.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-gcfg-hmwx-wq5h?

GHSA-gcfg-hmwx-wq5h affects the following packages: nategood/httpful (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-gcfg-hmwx-wq5h?

Update nategood/httpful to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gcfg-hmwx-wq5h is resolved across your whole dependency graph.

How do I detect GHSA-gcfg-hmwx-wq5h in my Packagist dependencies?

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

How do I mitigate GHSA-gcfg-hmwx-wq5h 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.

How does O3 Security protect against GHSA-gcfg-hmwx-wq5h?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gcfg-hmwx-wq5h can be triaged on real exposure rather than presence alone.

Is GHSA-gcfg-hmwx-wq5h actively exploited in the wild?

No public exploit code has been indexed for GHSA-gcfg-hmwx-wq5h 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.

When was GHSA-gcfg-hmwx-wq5h published, and has it been updated?

GHSA-gcfg-hmwx-wq5h was published on September 9, 2024 and was last updated on December 1, 2024. 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

HIGH severity

GHSA-gcfg-hmwx-wq5h — nategood/httpful

HIGHFix: nategood/httpful@44c880e

GHSA-gcfg-hmwx-wq5h is a high-severity (CVSS 7.4) vulnerability in nategood/httpful. A fix is available for nategood/httpful — see the affected versions and patch details below.

Httpful is Missing Certificate Validation

Published

Sep 9, 2024

Updated

Dec 1, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Dec 1, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘nategood/httpful

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

Httpful has Insecure HTTPS Connections due to Missing Default Certificate Validation

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`nategood/httpful`	all versions	1.0.0`composer require nategood/httpful:^1.0.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nategood/httpful, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update nategood/httpful to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gcfg-hmwx-wq5h is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-gcfg-hmwx-wq5h can be triaged on real exposure rather than presence alone.

Tailored to GHSA-gcfg-hmwx-wq5h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Httpful has Insecure HTTPS Connections due to Missing Default Certificate Validation

O3 Security · Impact-Aware SCA

Is GHSA-gcfg-hmwx-wq5h in your dependencies?

O3 Security finds GHSA-gcfg-hmwx-wq5h across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works