Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <adarsh.jagadish.kamini@est.tech>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][wrynose][PATCH] python3: CVE-2026-3087 not applicable
Date: Tue, 16 Jun 2026 22:52:13 +0200	[thread overview]
Message-ID: <DJARS4H3NJRW.3IYS5C7IXM00@smile.fr> (raw)
In-Reply-To: <20260603105132.872256-1-adarsh.jagadish.kamini@est.tech>

On Wed Jun 3, 2026 at 12:51 PM CEST, Adarsh Jagadish Kamini via lists.openembedded.org wrote:
> From: Adarsh Jagadish Kamini <adarsh.jagadish.kamini@est.tech>
>
> CVE link: https://nvd.nist.gov/vuln/detail/CVE-2026-3087
>
> The CVE is only applicable to Windows OS
>
> Signed-off-by: Adarsh Jagadish Kamini <adarsh.jagadish.kamini@est.tech>
> ---

Hello,

Thanks for the patch, but I preferred to go with the 3.14.5 upgrade,
which includes the fix.

Regards,

>  meta/recipes-devtools/python/python3_3.14.4.bb | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-devtools/python/python3_3.14.4.bb b/meta/recipes-devtools/python/python3_3.14.4.bb
> index 71f590f630..84cd770f3b 100644
> --- a/meta/recipes-devtools/python/python3_3.14.4.bb
> +++ b/meta/recipes-devtools/python/python3_3.14.4.bb
> @@ -48,6 +48,8 @@ UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar"
>  
>  CVE_PRODUCT = "python:python python_software_foundation:python cpython"
>  
> +CVE_STATUS[CVE-2026-3087] = "not-applicable-platform: Issue only applies on Windows"
> +
>  PYTHON_MAJMIN = "3.14"
>  
>  S = "${UNPACKDIR}/Python-${PV}"


-- 
Yoann Congal
Smile ECS



      reply	other threads:[~2026-06-16 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-03 10:51 [OE-core][wrynose][PATCH] python3: CVE-2026-3087 not applicable Adarsh Jagadish Kamini
2026-06-16 20:52 ` Yoann Congal [this message]

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=DJARS4H3NJRW.3IYS5C7IXM00@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=adarsh.jagadish.kamini@est.tech \
    --cc=openembedded-core@lists.openembedded.org \
    /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