How severe is GHSA-hpj7-wq8m-9hgp?

No CVSS score has been assigned to GHSA-hpj7-wq8m-9hgp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-hpj7-wq8m-9hgp?

GHSA-hpj7-wq8m-9hgp affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-hpj7-wq8m-9hgp?

Update aiohttp to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hpj7-wq8m-9hgp is resolved across your whole dependency graph.

How do I detect GHSA-hpj7-wq8m-9hgp 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-hpj7-wq8m-9hgp if there is no patch (or I can't update yet)?

Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

Is GHSA-hpj7-wq8m-9hgp actively exploited in the wild?

No public exploit code has been indexed for GHSA-hpj7-wq8m-9hgp 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-hpj7-wq8m-9hgp?

GHSA-hpj7-wq8m-9hgp has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th 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-hpj7-wq8m-9hgp?

GHSA-hpj7-wq8m-9hgp is classified as Information Exposure (CWE-200), CWE-522 (CWE-522), Open Redirect (CWE-601). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hpj7-wq8m-9hgp published, and has it been updated?

GHSA-hpj7-wq8m-9hgp was published on June 15, 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: DigestAuthMiddleware Applies Credentials to Cross-Origin Redirect ChallengesGHSA-hpj7-wq8m-9hgp

Fix: aio-libs/aiohttp@38d1606

GHSA-hpj7-wq8m-9hgp is a Information Exposure vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below.

Also known asCVE-2026-54276PYSEC-2026-2109

Published

Jun 15, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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-hpj7-wq8m-9hgp.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs24th percentile — riskier than 24% 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

DigestAuthMiddleware can send an authentication response after following a cross-origin redirect.

Impact

If the client follows a redirect (the default option) to an attacker controlled domain, the attacker may be able to extract the auth digest.

This likely requires an open redirect vulnerability or similar on the target domain for an attacker to be able to execute. Further, the attacker is only receiving the digest, so should only be able to extract the user's credentials if the cryptography is weak or there is some kind of password reuse.

Workaround

Disable follow_redirects if this is a concern.

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

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

aiohttpaiohttp

≥ 3.12.0 && < 3.14.1

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.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hpj7-wq8m-9hgp is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.

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 HatLow

This Low impact information disclosure flaw in aiohttp's DigestAuthMiddleware allows an authentication response to be sent after a cross-origin redirect. Exploitation requires an existing open redirect vulnerability on the target domain and relies on weak cryptography or password reuse to extract user credentials from…

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-hpj7-wq8m-9hgp (CC BY 4.0)

Frequently Asked Questions

### Summary ``DigestAuthMiddleware`` can send an authentication response after following a cross-origin redirect. ### Impact If the client follows a redirect (the default option) to an attacker controlled domain, the attacker may be able to extract the auth digest. This likely requires an open redirect vulnerability or similar on the target domain for an attacker to be able to execute. Further, the attacker is only receiving the digest, so should only be able to extract the user's credentials if the cryptography is weak or there is some kind of password reuse. ### Workaround Disable ``fo

O3 Security · Impact-Aware SCA

Is GHSA-hpj7-wq8m-9hgp in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works