OESA-2026-4996: python3 security update

Published Nov 19, 2026
·
Updated

Python combines remarkable power with very clear syntax. It has modules, classes, exceptions, very high level dynamic data types, and dynamic typing. There are interfaces to many system calls and libraries, as well as to various windowing systems. New built-in modules are easily written in C or C++ (or other languages, depending on the chosen implementation). Python is also usable as an extension language for applications written in other languages that need easy-to-use scripting or automation interfaces. Security Fix(es):

http.cookiejar.CookieJar deleted a stored cookie when a response carried an already expired Set-Cookie header for it, using the Domain and Path attributes from the header without consulting the cookie policy. A server could therefore delete cookies belonging to other domains from a shared cookie jar, such as the one used by urllib's HTTPCookieProcessor. The fix consults the cookie policy before an expired cookie may delete an existing one, as required by RFC 6265 section 5.3.(CVE-2026-124249)

Affected Software

1 affected componentFixes available
openeuler/python3<3.11.6-46.oe2403sp3
3.11.6-46.oe2403sp3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openeuler/python3 to a version that resolves this vulnerability.

    Fixed in 3.11.6-46.oe2403sp3

Event History

Nov 19, 2026
Advisory Published
via OSV·01:43 AM
Data Sourced
via OSV·01:43 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which applications are realistically exposed to this issue?

Applications that use Python's http.cookiejar.CookieJar in a shared cookie jar, including urllib clients using HTTPCookieProcessor, may be exposed when they process responses from untrusted or attacker-controlled servers.

2

What does an attacker need to do to exploit it?

An attacker-controlled server needs to send an already expired Set-Cookie header with Domain and Path attributes crafted to target a cookie already stored in the shared cookie jar. The vulnerable behavior could delete cookies belonging to other domains.

3

What is the security impact?

The issue affects cookie integrity: a malicious response can cause deletion of cookies for other domains from a shared cookie jar. The provided vector indicates low impact to vulnerable-system integrity and no stated confidentiality or availability impact.

4

What is the mitigation if the update cannot be applied immediately?

Avoid sharing a CookieJar across requests to untrusted servers and cookies for unrelated domains. Restricting the cookie jar to trusted response sources reduces the opportunity for a malicious server to submit crafted expired Set-Cookie headers.

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