How severe is GHSA-7mw3-79jq-xc7f?

No CVSS score has been assigned to GHSA-7mw3-79jq-xc7f yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7mw3-79jq-xc7f?

GHSA-7mw3-79jq-xc7f affects the following packages: aiograpi (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-7mw3-79jq-xc7f?

Update aiograpi to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7mw3-79jq-xc7f is resolved across your whole dependency graph.

How do I detect GHSA-7mw3-79jq-xc7f in my PyPI dependencies?

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

How do I mitigate GHSA-7mw3-79jq-xc7f if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is GHSA-7mw3-79jq-xc7f actively exploited in the wild?

No public exploit code has been indexed for GHSA-7mw3-79jq-xc7f 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-7mw3-79jq-xc7f published, and has it been updated?

GHSA-7mw3-79jq-xc7f was published on May 6, 2026 and was last updated on May 6, 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

aiograpi has dependency on vulnerable orjson 3.11.4 (CVE-2025-67221)GHSA-7mw3-79jq-xc7f

GHSA-7mw3-79jq-xc7f is a remote code execution vulnerability in aiograpi. A fix is available for aiograpi — see the affected versions and patch details below.

Published

May 6, 2026

Updated

May 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Real-World Exposure

1 pkg affected

🐍aiograpi

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

Impact

aiograpi 0.6.6 / 0.7.0 / 0.7.1 declared orjson==3.11.6 (and later ==3.11.8) in requirements.txt but setup.py carried a hard-coded duplicate requirements = [...] list that was never updated and still pinned orjson==3.11.4.

When setuptools builds the source distribution it reads the metadata from setup.py, not from requirements.txt. So pip install aiograpi==0.6.6 (or 0.7.0 / 0.7.1) actually pulls orjson==3.11.4 — a version vulnerable to CVE-2025-67221 (stack overflow in orjson.dumps on deeply nested JSON inputs).

Practical exploitability

Low in the typical aiograpi flow: orjson is used to encode request bodies aiograpi itself constructs and to decode responses returned by Instagram. An attacker would need to coerce aiograpi to encode an attacker-controlled deeply-nested Python structure or to decode an attacker-supplied stream — not the normal call shape.

However any caller doing client.public_request(...) or similar with caller-controlled payloads, or any caller passing aiograpi-decoded last_json into recursive serialization, may hit the unbounded recursion. The patched orjson rejects deeply-nested inputs cleanly.

Patches

Fixed in aiograpi 0.7.2 by migrating to pyproject.toml (PEP 621) — single source of truth for dependencies. PyPI installs of 0.7.2 and later resolve orjson==3.11.8 correctly.

Workarounds

Force-install a non-vulnerable orjson alongside the affected aiograpi version:

pip install 'aiograpi==0.7.1' 'orjson>=3.11.6'

Or just upgrade to a fixed aiograpi:

pip install -U 'aiograpi>=0.7.2'

Resources

orjson CVE-2025-67221 advisory: https://github.com/ijl/orjson/security/advisories
aiograpi 0.7.2 changelog (security section): https://github.com/subzeroid/aiograpi/blob/main/CHANGELOG.md#072--2026-04-27

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`aiograpi`	≥ 0.6.6&&< 0.7.2	0.7.2`pip install --upgrade 'aiograpi==0.7.2'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aiograpi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aiograpi to 0.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7mw3-79jq-xc7f is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Frequently Asked Questions

## Impact aiograpi 0.6.6 / 0.7.0 / 0.7.1 declared `orjson==3.11.6` (and later `==3.11.8`) in `requirements.txt` but `setup.py` carried a hard-coded duplicate `requirements = [...]` list that was never updated and still pinned `orjson==3.11.4`. When `setuptools` builds the source distribution it reads the metadata from `setup.py`, not from `requirements.txt`. So `pip install aiograpi==0.6.6` (or 0.7.0 / 0.7.1) actually pulls `orjson==3.11.4` — a version vulnerable to **CVE-2025-67221** (stack overflow in `orjson.dumps` on deeply nested JSON inputs). ## Practical exploitability Low in the ty

O3 Security · Impact-Aware SCA

Is GHSA-7mw3-79jq-xc7f in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works