How severe is GHSA-ggxf-37hm-9wqf?

GHSA-ggxf-37hm-9wqf has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-ggxf-37hm-9wqf?

GHSA-ggxf-37hm-9wqf affects the following packages: instagrapi (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-ggxf-37hm-9wqf?

Update instagrapi to 2.6.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ggxf-37hm-9wqf is resolved across your whole dependency graph.

How do I detect GHSA-ggxf-37hm-9wqf in my PyPI dependencies?

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

How do I mitigate GHSA-ggxf-37hm-9wqf 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-ggxf-37hm-9wqf actively exploited in the wild?

No public exploit code has been indexed for GHSA-ggxf-37hm-9wqf 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-ggxf-37hm-9wqf published, and has it been updated?

GHSA-ggxf-37hm-9wqf was published on May 23, 2026 and was last updated on May 23, 2026. 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

MEDIUM severity

GHSA-ggxf-37hm-9wqf — instagrapi

MEDIUM

GHSA-ggxf-37hm-9wqf is a medium-severity (CVSS 6.5) vulnerability in instagrapi. A fix is available for instagrapi — see the affected versions and patch details below.

instagrapi: Unsafe signup challenge path handling in instagrapi

Published

May 23, 2026

Updated

May 23, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 23, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍instagrapi

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

instagrapi versions before 2.6.9 accepted server-supplied signup challenge paths and used them to build request URLs before validating that the paths were relative Instagram API paths. A malicious or tampered challenge payload could cause challenge handling requests to be sent outside the intended Instagram host with the client's existing session headers. Version 2.6.9 validates challenge paths before building URLs, solving captcha challenges, or submitting phone/SMS challenge forms.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`instagrapi`	all versions	2.6.9`pip install --upgrade 'instagrapi==2.6.9'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for instagrapi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update instagrapi to 2.6.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ggxf-37hm-9wqf 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.

Frequently Asked Questions

instagrapi versions before 2.6.9 accepted server-supplied signup challenge paths and used them to build request URLs before validating that the paths were relative Instagram API paths. A malicious or tampered challenge payload could cause challenge handling requests to be sent outside the intended Instagram host with the client\'s existing session headers. Version 2.6.9 validates challenge paths before building URLs, solving captcha challenges, or submitting phone/SMS challenge forms.

O3 Security · Impact-Aware SCA

Is GHSA-ggxf-37hm-9wqf in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works