From: "Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)" <devanshp@cisco.com>
To: openembedded-core@lists.openembedded.org
Cc: xe-linux-external@cisco.com
Subject: [OE-core][PATCH] python3: correct CVE_PRODUCT mapping
Date: Wed, 26 Aug 2026 00:53:48 -0700 [thread overview]
Message-ID: <20260826075348.64166-1-devanshp@cisco.com> (raw)
From: Devansh Patel <devanshp@cisco.com>
The current mapping qualifies the generic Python product but leaves cpython
vendor-wildcarded. python:python is the active NVD dictionary CPE and
configuration identity. Keep python_software_foundation:python for
historical NVD configurations.
Qualify OE-Core's retained CPython alias as python:cpython, the deprecated
NVD dictionary CPE spelling that now points to python:python.
Add python_software_foundation:cpython for authoritative Python CNA affected
data for the same CPython source. It has no dictionary record.
This changes the generated CPython identities to exact CPEs, but the frozen
sbom-cve-check database leaves the 188-entry CVE report unchanged, with no
current CVE delta.
Signed-off-by: Devansh Patel <devanshp@cisco.com>
---
meta/recipes-devtools/python/python3_3.14.7.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-devtools/python/python3_3.14.7.bb b/meta/recipes-devtools/python/python3_3.14.7.bb
index 1eef256a83..5764359a02 100644
--- a/meta/recipes-devtools/python/python3_3.14.7.bb
+++ b/meta/recipes-devtools/python/python3_3.14.7.bb
@@ -36,7 +36,7 @@ UPSTREAM_CHECK_REGEX = "[Pp]ython-(?P<pver>\d+(\.\d+)+).tar"
# maintenance branches.
inherit upstream-stable-release-point
-CVE_PRODUCT = "python:python python_software_foundation:python cpython"
+CVE_PRODUCT = "python:python python_software_foundation:python python:cpython python_software_foundation:cpython"
PYTHON_MAJMIN = "3.14"
--
2.35.6
reply other threads:[~2026-08-26 7:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260826075348.64166-1-devanshp@cisco.com \
--to=devanshp@cisco.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=xe-linux-external@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