OESA-2026-4996: python3 security update
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
openeuler/python3to a version that resolves this vulnerability.Fixed in 3.11.6-46.oe2403sp3
Event History
Frequently Asked Questions
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.
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.
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.
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.