Skip to contentSkip to conversation

python3-aiohttp: correct CVE_PRODUCT mapping

PATCH New Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco) 1 participant 1 message Aug 24

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 python3-aiohttp: correct CVE_PRODUCT mapping

From: Devansh Patel <[email protected]>

The current "aiohttp" mapping emits the wildcard-vendor *:aiohttp CPE instead of the exact NVD identity for the packaged aio-libs/aiohttp source.

Use "aiohttp:aiohttp", which is both an NVD dictionary CPE and an NVD configuration identity. CNA affected data uses "aio-libs:aiohttp" and remains covered by scanner aliases. With sbom-cve-check 1.3.3 and the pinned 2026-08-12 data, the generated identity changes but the current CVE report does not.

---
 meta-python/recipes-devtools/python/python3-aiohttp_3.14.3.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta-python/recipes-devtools/python/python3-aiohttp_3.14.3.bb +1 -1
index 033fc7c804..b862076869 100644
@@ -6,7 +6,7 @@ LIC_FILES_CHKSUM = "file://LICENSE.txt;md5=b5e9e27554f71f0f132919037cb967b2"
 
 SRC_URI[sha256sum] = "9491196535a88924a60afd5b5f434b5b203b6cc616250878dbdb223a8f7844bc"
 
-CVE_PRODUCT = "aiohttp"
+CVE_PRODUCT = "aiohttp:aiohttp"
 CVE_STATUS_GROUPS = "CVE_AIOHTTP_FIX_3_13_4"
 CVE_AIOHTTP_FIX_3_13_4[status] = "fixed-version: fixed in 3.13.4"
 CVE_AIOHTTP_FIX_3_13_4 = "CVE-2026-22815 CVE-2026-34513 CVE-2026-34514 \
Signature · 1 line
2.35.6