ALPINE-CVE-2026-113593: Low severity alpine/py3-django vulnerability

Published Nov 3, 2026
·
Updated

An issue was discovered in Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19. The django.middleware.cache.UpdateCacheMiddleware and the django.views.decorators.cache.cachepage() decorator generate identical cache keys for requests that omit a header listed in the response’s Vary header and requests that include that header with an empty value, potentially allowing remote attackers to access private data cached for another request. Earlier, unsupported Django series (such as 5.1.x, 5.0.x, and 4.2.x) were not evaluated and may also be affected. Django would like to thank Andrew Gonzalez for reporting this issue.

Affected Software

1 affected componentFixes available
alpine/py3-django<5.2.19-r0
5.2.19-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade alpine/py3-django to a version that resolves this vulnerability.

    Fixed in 5.2.19-r0
  2. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 6.1.3
  3. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 6.0.10
  4. Upgrade

    Upgrade Django to a version that resolves this vulnerability.

    Fixed in 5.2.19

Event History

Nov 3, 2026
CVE Published
via OSV·04:17 PM
Data Sourced
via OSV·04:17 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What conditions are needed for private data to be exposed?

The application must use UpdateCacheMiddleware or the cache_page() decorator and cache a response whose Vary header lists a header relevant to the response. A remote attacker may then distinguish between omitting that header and supplying it with an empty value to receive data cached for another request.

2

Which Django versions include the fix?

Upgrade to Django 6.1.3 or later, 6.0.10 or later, or 5.2.19 or later. Django 6.1 before 6.1.3, 6.0 before 6.0.10, and 5.2 before 5.2.19 are affected.

3

How can I identify endpoints that may be at risk?

Review endpoints cached through UpdateCacheMiddleware or cache_page() and identify cached responses that include a Vary header and may contain private data. Unsupported Django series, including 5.1.x, 5.0.x, and 4.2.x, were not evaluated and may also be affected.

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