From: "Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco)" <devanshp@cisco.com>
To: meta-virtualization@lists.yoctoproject.org
Cc: xe-linux-external@cisco.com
Subject: [meta-virtualization][wrynose][PATCH] docker-compose: add CVE_PRODUCT and CVE_STATUS for CVE-2025-62725
Date: Tue, 4 Aug 2026 22:04:59 -0700 [thread overview]
Message-ID: <20260805050459.1743048-1-devanshp@cisco.com> (raw)
From: "mark.yang" <mark.yang@lge.com>
Add CVE_PRODUCT to docker-compose that matches CPE.
<vendor>:<product> must be set to docker:compose for proper matching.
CVE-2025-62725 was fixed in 2.40.2, but its record encodes the range as
a plain "< 2.40.2" version string that automated version comparison
cannot use, so mark it as fixed-version.
Signed-off-by: mark.yang <mark.yang@lge.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
(cherry picked from commit e456f38266f55e32521903cddd8a0f9fee2fd5eb)
Signed-off-by: Devansh Patel <devanshp@cisco.com>
---
recipes-containers/docker-compose/docker-compose_git.bb | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/recipes-containers/docker-compose/docker-compose_git.bb b/recipes-containers/docker-compose/docker-compose_git.bb
index 3eb78c04..aa61d245 100644
--- a/recipes-containers/docker-compose/docker-compose_git.bb
+++ b/recipes-containers/docker-compose/docker-compose_git.bb
@@ -30,6 +30,10 @@ GO_IMPORT = "import"
PV = "5.1.0"
+CVE_PRODUCT = "docker:compose"
+
+CVE_STATUS[CVE-2025-62725] = "fixed-version: fixed in 2.40.2"
+
COMPOSE_PKG = "github.com/docker/compose/v2"
# go-mod-discovery configuration
--
2.53.0
next reply other threads:[~2026-08-05 5:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 5:04 Devansh Patel -X (devanshp - E INFOCHIPS PRIVATE LIMITED at Cisco) [this message]
2026-08-05 21:50 ` [meta-virtualization][wrynose][PATCH] docker-compose: add CVE_PRODUCT and CVE_STATUS for CVE-2025-62725 Bruce Ashfield
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=20260805050459.1743048-1-devanshp@cisco.com \
--to=devanshp@cisco.com \
--cc=meta-virtualization@lists.yoctoproject.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