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)?

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.

How does O3 Security protect against GHSA-hpj7-wq8m-9hgp?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hpj7-wq8m-9hgp can be triaged on real exposure rather than presence alone.

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

GHSA-hpj7-wq8m-9hgp — aiohttp

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.

aiohttp: DigestAuthMiddleware Applies Credentials to Cross-Origin Redirect Challenges

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 Sep 19, 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

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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'`

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
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-hpj7-wq8m-9hgp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-hpj7-wq8m-9hgp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds GHSA-hpj7-wq8m-9hgp across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works