Information Disclosure in aiohttp (CVE-2026-54276)
Summary
Vulnerability in aiohttp (CVE-2026-54276). Risk of unauthorized operations or information disclosure. Exploitable via DigestAuthMiddleware. Mitigation: upgrade to 3.14.1 or later.
Original description
The description as published by the source.
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
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54276 has been found in aiohttp.
Attackers can target a specific entry point like DigestAuthMiddleware over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade aiohttp to 3.14.1 or later.
If unsure, ask your IT team or search "aiohttp CVE-2026-54276" on the vendor's site.
CVE-2026-54276 (aiohttp) — CWE-200 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: DigestAuthMiddleware / follow_redirects
Patched: 3.14.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Information disclosure (CWE-200) exists in aiohttp. Attackers reach the vulnerable code path via DigestAuthMiddleware without authentication.
Check the vendor advisory for the affected versions of aiohttp. Attack surface: DigestAuthMiddleware / follow_redirects.
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.
Update to 3.14.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'aiohttp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'aiohttp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
aiohttpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade aiohttp to 3.14.1ステージング環境で 3.14.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Ubuntu UBUNTU-CVE-2026-54276 python-aiohttp
References
- patch security-advisories@github.com
- patch security-advisories@github.com
- web github.com