How severe is GHSA-hg6j-4rv6-33pg?

No CVSS score has been assigned to GHSA-hg6j-4rv6-33pg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hg6j-4rv6-33pg?

GHSA-hg6j-4rv6-33pg affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-hg6j-4rv6-33pg?

Update aiohttp to 3.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hg6j-4rv6-33pg is resolved across your whole dependency graph.

How do I detect GHSA-hg6j-4rv6-33pg in my PyPI dependencies?

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

How do I mitigate GHSA-hg6j-4rv6-33pg 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-hg6j-4rv6-33pg actively exploited in the wild?

No public exploit code has been indexed for GHSA-hg6j-4rv6-33pg 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.

What is the EPSS score for GHSA-hg6j-4rv6-33pg?

GHSA-hg6j-4rv6-33pg has an EPSS (Exploit Prediction Scoring System) score of 0.1%, placing it in the 4th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hg6j-4rv6-33pg?

GHSA-hg6j-4rv6-33pg is classified as CWE-346 (CWE-346). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hg6j-4rv6-33pg published, and has it been updated?

GHSA-hg6j-4rv6-33pg was published on June 3, 2026 and was last updated on September 10, 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

AIOHTTP is vulnerable to cross-origin redirect with per-request cookiesGHSA-hg6j-4rv6-33pg

Fix: aio-libs/aiohttp@f54c408

GHSA-hg6j-4rv6-33pg is a CWE-346 vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below.

Also known asCVE-2026-47265PYSEC-2026-2105

Published

Jun 3, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hg6j-4rv6-33pg.

EPSS Exploitation Probability

via FIRST.org ↗

0.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs4th percentile — riskier than 4% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍aiohttp

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

Cookies set with the cookies parameter on requests are sent after following a cross-origin redirect.

Impact

If a developer uses the cookies parameter on a per-request basis then sensitive data might be leaked to an attacker if they manage to control a redirect.

Workaround

If unable to upgrade, using a Cookie header in the headers parameter is not vulnerable.

Patch: https://github.com/aio-libs/aiohttp/commit/f54c40851b0d6c4bbdab97ba518a223adda32478

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

aiohttpaiohttp

< 3.14.0

range

Detection & mitigation playbook

Open-source dependency

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

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

AIOHTTP, as utilized in Red Hat products, is susceptible to a Moderate information disclosure flaw. This vulnerability arises when the `cookies` parameter is used for per-request cookie handling, potentially exposing sensitive data if a cross-origin redirect is controlled by an attacker. This specific usage pattern of…

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for GHSA-hg6j-4rv6-33pg (CC BY 4.0)

Frequently Asked Questions

### Summary Cookies set with the `cookies` parameter on requests are sent after following a cross-origin redirect. ### Impact If a developer uses the `cookies` parameter on a per-request basis then sensitive data might be leaked to an attacker if they manage to control a redirect. ### Workaround If unable to upgrade, using a `Cookie` header in the `headers` parameter is not vulnerable. ----- Patch: https://github.com/aio-libs/aiohttp/commit/f54c40851b0d6c4bbdab97ba518a223adda32478

O3 Security · Impact-Aware SCA

Is GHSA-hg6j-4rv6-33pg in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works