From: "Yoann Congal" <yoann.congal@smile.fr>
To: <jeremy.rosen@smile.fr>, <sudumbha@cisco.com>,
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][scarthgap][PATCH] python3-urllib3: fix CVE-2026-44431
Date: Mon, 06 Jul 2026 19:10:04 +0200 [thread overview]
Message-ID: <DJRNKXABC7Z8.2LMS2YNVK56HC@smile.fr> (raw)
In-Reply-To: <DJ6ZX1JZMT8S.BM5LO9MCVMTJ@smile.fr>
On Fri Jun 12, 2026 at 12:24 PM CEST, Jérémy Rosen via lists.openembedded.org wrote:
> Hello Sudhir
>
> This CVE also affects wrynose and I could not find any submission for
> wrynose
>
> please submit for wrynose and once it is affected ping here
>
> Thanks a lot
> Jérémy
Hello Sudhir,
Gentle ping for this patch.
Regards,
>
> On Mon Jun 1, 2026 at 8:11 PM CEST, Sudhir Dumbhare via lists.openembedded.org wrote:
>> From: Sudhir Dumbhare <sudumbha@cisco.com>
>>
>> Applies the upstream fix [1] referenced in [2] and addresses the
>> sensitive-header redirect handling issue in proxied low-level urllib3 requests.
>>
>> [1] https://github.com/urllib3/urllib3/commit/5ec0de499b9166ca71c65ab04f2a7e4eb0d66fcc
>> [2] https://ubuntu.com/security/CVE-2026-44431
>>
>> References:
>> https://nvd.nist.gov/vuln/detail/CVE-2026-44431
>>
>> Signed-off-by: Sudhir Dumbhare <sudumbha@cisco.com>
>> ---
>> .../python3-urllib3/CVE-2026-44431.patch | 163 ++++++++++++++++++
>> .../python/python3-urllib3_2.2.2.bb | 1 +
>> 2 files changed, 164 insertions(+)
>> create mode 100644 meta/recipes-devtools/python/python3-urllib3/CVE-2026-44431.patch
>>
--
Yoann Congal
Smile ECS
next prev parent reply other threads:[~2026-07-06 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-01 18:11 [OE-core][scarthgap][PATCH] python3-urllib3: fix CVE-2026-44431 Sudhir Dumbhare -X (sudumbha - E INFOCHIPS PRIVATE LIMITED at Cisco)
2026-06-12 10:24 ` Jeremy Rosen
2026-07-06 17:10 ` Yoann Congal [this message]
2026-07-08 11:53 ` [scarthgap][PATCH] " Sudhir Dumbhare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DJRNKXABC7Z8.2LMS2YNVK56HC@smile.fr \
--to=yoann.congal@smile.fr \
--cc=jeremy.rosen@smile.fr \
--cc=openembedded-core@lists.openembedded.org \
--cc=sudumbha@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox