CVE-2026-54276: AIOHTTP: DigestAuthMiddleware Applies Credentials to Cross-Origin Redirect Challenges

Published Jun 15, 2026
·
Updated

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 followredirects if this is a concern.

-----

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

Other sources

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, DigestAuthMiddleware can send an authentication response after following a cross-origin redirect. 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. This vulnerability is fixed in 3.14.1.

MITRE

Affected Software

2 affected componentsFixes available
pip/aiohttp<=3.14.0
3.14.1
aiohttp aiohttp<3.14.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.1
  2. Upgrade

    Upgrade aio-libs/aiohttp to a version that resolves this vulnerability.

    Fixed in 3.14.1Patch 38d16060037e1bfcd6d677abababa3c2a4bb58fa
  3. Configuration

    Disable follow_redirects to prevent DigestAuthMiddleware from following cross-origin redirect challenges that could allow an attacker to extract the auth digest.

    AIOHTTP DigestAuthMiddleware follow_redirects = false

Event History

Jun 15, 2026
Advisory Published
via GitHub·08:09 PM
Data Sourced
via GitHub·08:09 PM
DescriptionWeaknessAffected Software
Jun 22, 2026
CVE Published
via MITRE·04:36 PM
Data Sourced
via MITRE·04:36 PM
DescriptionWeakness
Data Sourced
via NVD·06:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-54276?

CVE-2026-54276 has a risk rating of 27.

2

What is CVE-2026-54276 about?

CVE-2026-54276 involves the `DigestAuthMiddleware` potentially allowing authentication responses to be sent after following a cross-origin redirect.

3

How does CVE-2026-54276 impact users?

The vulnerability could allow an attacker to extract the authentication digest if a user follows a redirect to a malicious domain.

4

How do I fix CVE-2026-54276?

To fix CVE-2026-54276, update your aiohttp library to the latest version that addresses this vulnerability.

5

What is the default behavior that leads to CVE-2026-54276?

The default behavior of following redirects in aiohttp can expose users to this vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203