Skip to contentSkip to conversation

graphene: set status for CVE-2026-81281

PATCH New Peter Marko 1 participant 4 messages Sep 28

lore
Share & tools
lore
#0 lore raw

PATCH 1/4 graphene: set status for CVE-2026-81281

From: Peter Marko <[email protected]>

Per description in [1] and also per [2] this is CVE is for WordPress theme.

[1] https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/81xxx/CVE-2026-81281.json
[2] https://security-tracker.debian.org/tracker/CVE-2026-81281

(From OE-Core rev: 41cfe5df728cfeef3adac69f0bbdace70c339e78)

---
 meta/recipes-graphics/graphene/graphene_1.10.8.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-graphics/graphene/graphene_1.10.8.bb +1 -0
index 7aa72b4a78..0d526d3d76 100644
@@ -28,3 +28,4 @@ FILES:${PN} += "${libdir}/graphene-1.0"
 BBCLASSEXTEND = "native nativesdk"
 
 CVE_STATUS[CVE-2024-1984] = "cpe-incorrect: issue in a WordPress theme"
+CVE_STATUS[CVE-2026-81281] = "cpe-incorrect: issue in a WordPress theme"
#1 lore raw

PATCH 2/4 openssh: set status for CVE-2026-55655

From: Peter Marko <[email protected]>

Per [1] and [2] this this is only problem in RedHet patches.

[1] https://security-tracker.debian.org/tracker/CVE-2026-55655
[2] https://ubuntu.com/security/CVE-2026-55655

(From OE-Core rev: 9ea8649149e711668b85c7e35cb7c259437e8c0e)

---
 meta/recipes-connectivity/openssh/openssh_10.3p1.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-connectivity/openssh/openssh_10.3p1.bb +1 -0
index e6bc9e9a5b..9793e3fa6d 100644
@@ -46,6 +46,7 @@ CVE_STATUS[CVE-2023-51767] = "upstream-wontfix: It was demonstrated on modified
 CVE_STATUS[CVE-2026-3497] = "not-applicable-platform: Only affects GSSAPI Key Exchange patches used by some Linux distributions and does not exist in upstream openssh."
 CVE_STATUS[CVE-2026-55653] = "not-applicable-platform: Only applies to RHEL FIPS patches."
 CVE_STATUS[CVE-2026-59998] = "${@bb.utils.contains('PACKAGECONFIG', 'kerberos', 'unpatched', 'not-applicable-config: GSSAPI/Kerberos support is disabled in the default OpenSSH configuration', d)}"
+CVE_STATUS[CVE-2026-55655] = "not-applicable-platform: Only applies to RHEL patches."
 
 PAM_SRC_URI = "file://sshd"
 
#2 lore raw

PATCH 3/4 openssh: set status for CVE-2026-55654

In reply to Peter Marko

From: Peter Marko <[email protected]>

Per desctiption in [1] (which is different than description in [2]), this is RedHat patches.
Also [3] suggests this.

[1] https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/55xxx/CVE-2026-55654.json
[2] https://security-tracker.debian.org/tracker/CVE-2026-55654
[3] https://ubuntu.com/security/CVE-2026-55654

(From OE-Core rev: 389919ea7927962a61a5aaa7b641c5b60af560e0)

---
 meta/recipes-connectivity/openssh/openssh_10.3p1.bb | 1 +
 1 file changed, 1 insertion(+)
meta/recipes-connectivity/openssh/openssh_10.3p1.bb +1 -0
index 9793e3fa6d..c53100cd99 100644
@@ -46,6 +46,7 @@ CVE_STATUS[CVE-2023-51767] = "upstream-wontfix: It was demonstrated on modified
 CVE_STATUS[CVE-2026-3497] = "not-applicable-platform: Only affects GSSAPI Key Exchange patches used by some Linux distributions and does not exist in upstream openssh."
 CVE_STATUS[CVE-2026-55653] = "not-applicable-platform: Only applies to RHEL FIPS patches."
 CVE_STATUS[CVE-2026-59998] = "${@bb.utils.contains('PACKAGECONFIG', 'kerberos', 'unpatched', 'not-applicable-config: GSSAPI/Kerberos support is disabled in the default OpenSSH configuration', d)}"
+CVE_STATUS[CVE-2026-55654] = "not-applicable-platform: Only applies to RHEL patches."
 CVE_STATUS[CVE-2026-55655] = "not-applicable-platform: Only applies to RHEL patches."
 
 PAM_SRC_URI = "file://sshd"
#3 lore raw

PATCH 4/4 xserver-xorg: set status for CVE-2026-55999 and CVE-2026-56000

In reply to Peter Marko

From: Peter Marko <[email protected]>

Per [1], CVE-2026-55999 was fixed by [2] which was backported as [3]. Per [4], CVE-2026-56000 was fixed by [5] which was backported as [6].

[1] https://security-tracker.debian.org/tracker/CVE-2026-55999
[2] https://gitlab.freedesktop.org/xorg/xserver/-/commit/fbf7bac22e2c6bd627fb042742a23318263edae1
[3] https://gitlab.freedesktop.org/xorg/xserver/-/commit/0f1f4bcbfb1f23b800dfe386782d3a0f05b6756f
[4] https://security-tracker.debian.org/tracker/CVE-2026-56000
[5] https://gitlab.freedesktop.org/xorg/xserver/-/commit/2779affbdb4354e894f490e56f962527d6125043
[6] https://gitlab.freedesktop.org/xorg/xserver/-/commit/d6d96084f305a142eb3db7f720d7edd21e4c98b4

cvelistV5 has correct version identification, so CNA (SUSE) has it correct, too.
NVD however shows non-existing version 21.2.24 (probably from CVE description), so it's showing up in reports as unfixed.

(From OE-Core rev: b6ab21c7e75acb65a3993565929be9c72f4a3d39)

---
 meta/recipes-graphics/xorg-xserver/xserver-xorg.inc | 2 ++
 1 file changed, 2 insertions(+)
meta/recipes-graphics/xorg-xserver/xserver-xorg.inc +2 -0
index 782c1f76ca..419e539a54 100644
@@ -31,6 +31,8 @@ available for this flaw."
 CVE_STATUS[CVE-2022-3553] = "cpe-incorrect: This is specific to XQuartz, which is the macOS X server port"
 CVE_STATUS[CVE-2026-34000] = "fixed-version: fixed since v21.1.22"
 CVE_STATUS[CVE-2026-34002] = "fixed-version: fixed since v21.1.22"
+CVE_STATUS[CVE-2026-55999] = "fixed-version: fixed since v21.1.24"
+CVE_STATUS[CVE-2026-56000] = "fixed-version: fixed since v21.1.24"
 
 S = "${UNPACKDIR}/${XORG_PN}-${PV}"