How severe is GHSA-3vpc-4p9p-47hc?

No CVSS score has been assigned to GHSA-3vpc-4p9p-47hc yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3vpc-4p9p-47hc?

GHSA-3vpc-4p9p-47hc affects the following packages: curl-cffi (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-3vpc-4p9p-47hc?

Update curl-cffi to 0.7.0b6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vpc-4p9p-47hc is resolved across your whole dependency graph.

How do I detect GHSA-3vpc-4p9p-47hc in my PyPI dependencies?

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

How do I mitigate GHSA-3vpc-4p9p-47hc 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-3vpc-4p9p-47hc?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3vpc-4p9p-47hc can be triaged on real exposure rather than presence alone.

Is GHSA-3vpc-4p9p-47hc actively exploited in the wild?

No public exploit code has been indexed for GHSA-3vpc-4p9p-47hc 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-3vpc-4p9p-47hc published, and has it been updated?

GHSA-3vpc-4p9p-47hc was published on October 22, 2024 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

GHSA-3vpc-4p9p-47hc — curl-cffi

GHSA-3vpc-4p9p-47hc is a security vulnerability in curl-cffi. A fix is available for curl-cffi — see the affected versions and patch details below.

curl_cffi bundles a version of libcurl affected by High Severity vulnerability

Published

Oct 22, 2024

Updated

Dec 2, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐍curl-cffi

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

Description

Summary

curl_cffi is potentially affected by High Severity vulnerability (CVE-2023-38545) in libcurl<8.4.0

Details

HIGH severity vulnerability in curl and libcurl: announcement Details are still unknown, but seems it will be a major issue as it's advertised by curl devs as "probably the worst curl security flaw in a long time". A patched version (8.4.0) and details will be published around 06:00 UTC on October 11. curl_cffi wheels on PyPI ship with libcurl 7.84.0

PoC

https://inspector.pypi.io/project/curl-cffi/0.5.10b2/packages/56/ae/eb7d39ad234f1f44650b910757d5aa696feff413d327c8328223ce78cb76/curl_cffi-0.5.10b2-cp37-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl/curl_cffi/include/curl/curlver.h

Resolution

Versions after 0.7 bundles with libcurl>=8.5, which is not affected by this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`curl-cffi`	all versions	0.7.0b6`pip install --upgrade 'curl-cffi==0.7.0b6'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for curl-cffi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update curl-cffi to 0.7.0b6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vpc-4p9p-47hc 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-3vpc-4p9p-47hc can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3vpc-4p9p-47hc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary curl_cffi is potentially affected by High Severity vulnerability (CVE-2023-38545) in libcurl<8.4.0 ### Details HIGH severity vulnerability in curl and libcurl: [announcement](https://github.com/curl/curl/discussions/12026#discussioncomment-7195548) Details are still unknown, but seems it will be a major issue as it's advertised by curl devs as "_probably the worst curl security flaw in a long time_". A patched version (8.4.0) and details will be published around 06:00 UTC on October 11. curl_cffi wheels on PyPI ship with libcurl 7.84.0 ### PoC [https://inspector.pypi.io/project/c

O3 Security · Impact-Aware SCA

Is GHSA-3vpc-4p9p-47hc in your dependencies?

O3 Security finds GHSA-3vpc-4p9p-47hc across PyPI 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