EUVD-2026-36272
GHSA-jh37-x3fv-4x72
Severity by source
AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Primary rating from Vendor (https://github.com/subzeroid/aiograpi) · only source for this CVE.
CVSS VectorVendor: https://github.com/subzeroid/aiograpi
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Lifecycle Timeline
2DescriptionCVE.org
aiograpi versions before 0.9.10 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 0.9.10 validates challenge paths before building URLs, solving captcha challenges, or submitting phone/SMS challenge forms.
AnalysisAI
Server-Side Request Forgery in aiograpi before 0.9.10 allows an adjacent-network attacker to redirect Instagram challenge-handling HTTP requests to arbitrary attacker-controlled hosts, exfiltrating the client's active session headers including authentication tokens. The library trusted server-supplied signup challenge paths and used them verbatim to construct outbound URLs without first verifying the path remained within Instagram's API domain. No public exploit code has been identified and this CVE does not appear in the CISA KEV catalog, but the high confidentiality impact (CVSS C:H) reflects that session credential theft is the direct outcome of a successful attack.
Technical ContextAI
aiograpi is an asynchronous Python client library (pip package: aiograpi) for the Instagram Private API. During account signup or challenge flows, Instagram's API returns challenge payloads that include path values. Prior to version 0.9.10, the library concatenated these server-supplied paths directly into outbound request URLs - covering captcha challenge resolution and phone/SMS challenge form submission - without validating that the resulting URL remained scoped to a legitimate Instagram API host. This is a textbook CWE-918 (Server-Side Request Forgery) pattern: untrusted input from a server response is used to construct a subsequent outbound request without host-scope enforcement. The CPE identifier is pkg:pip/aiograpi, and the CVSS vector AV:A indicates exploitation requires adjacent-network positioning, consistent with a man-in-the-middle or response-tampering scenario during the challenge exchange.
RemediationAI
Upgrade aiograpi to version 0.9.10 or later, which validates that all server-supplied challenge paths are relative Instagram API paths before constructing any outbound URLs, solving captcha challenges, or submitting phone/SMS challenge forms. This is the primary and complete fix, confirmed by the vendor advisory at https://github.com/subzeroid/aiograpi/security/advisories/GHSA-jh37-x3fv-4x72. If immediate upgrade is not possible, a compensating control is to deploy the aiograpi client exclusively on network segments with strict egress filtering that denies outbound HTTPS to non-Instagram domains (e.g., *.instagram.com, *.cdninstagram.com whitelist); this would prevent exfiltration of session headers to attacker-controlled hosts, though it introduces operational risk of blocking legitimate API calls if the allowlist is misconfigured. Additionally, rotating session credentials (Instagram session tokens) after any period of operation on untrusted or shared networks reduces the value of credentials that may have already been exposed.
Same weakness CWE-918 – Server-Side Request Forgery (SSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today