Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Anuj Mittal <anuj.mittal@oss.qualcomm.com>
To: raj.khem@gmail.com, openembedded-devel@lists.openembedded.org
Subject: [PATCH 00/13] Scarthgap pull request
Date: Tue,  9 Jun 2026 18:19:42 +0530	[thread overview]
Message-ID: <cover.1781009217.git.anuj.mittal@oss.qualcomm.com> (raw)

Please merge these changes in scarthgap. Tested locally and on autobuilder.

https://autobuilder.yoctoproject.org/valkyrie/#/builders/81/builds/1547

The following changes since commit d8cc4e44001c7257273d290ce8c4496e93d32841:

  postgresql: upgrade 16.12 -> 16.14 (2026-05-25 08:05:43 +0530)

are available in the Git repository at:

  https://git.openembedded.org/meta-openembedded-contrib anujm/scarthgap
  https://git.openembedded.org/meta-openembedded-contrib/log/?h=anujm/scarthgap

for you to fetch changes up to b0c2c648a1af89e7a8dd4c2ec841f3bc0ed0ccb9:

  nginx: backport fix for CVE-2026-9256 (2026-06-09 11:37:19 +0530)

----------------------------------------------------------------

Ankur Tyagi (1):
  postfix: upgrade 3.8.16 -> 3.8.17

Gyorgy Sarvari (4):
  python3-paramiko: set CVE_PRODUCT
  python3-priority: set CVE_PRODUCT
  python3-pydantic: set CVE_PRODUCT
  python3-supervisor: set CVE_PRODUCT

Naman Jain (1):
  libssh: ignore CVE-2025-14821

Nelson Garcia (1):
  nginx: backport fix for CVE-2026-9256

Sudhir Dumbhare (6):
  python3-grpcio: Fix CVE-2024-7246
  python3-grpcio: set status for CVE-2026-33186
  python3-grpcio-tools: set status for CVE-2026-33186
  python3-grpcio-tools: set status for CVE-2024-7246
  python3-grpcio-tools: set status for CVE-2024-11407
  python3-tornado: Fix CVE-2026-31958

 .../{postfix_3.8.16.bb => postfix_3.8.17.bb}  |   2 +-
 .../recipes-support/libssh/libssh_0.10.6.bb   |   2 +
 .../python-priority/python3-priority_2.0.0.bb |   2 +
 .../python/python3-grpcio-tools_1.62.2.bb     |   4 +
 .../python/python3-grpcio/CVE-2024-7246.patch | 206 ++++++++++++++
 .../python/python3-grpcio_1.62.2.bb           |   3 +
 .../python/python3-paramiko_3.4.0.bb          |   2 +
 .../python/python3-pydantic_2.7.4.bb          |   2 +
 .../python/python3-supervisor_4.2.5.bb        |   1 +
 .../python3-tornado/CVE-2026-31958.patch      | 262 ++++++++++++++++++
 .../python/python3-tornado_6.4.2.bb           |   1 +
 .../nginx/nginx-1.24.0/CVE-2026-9256.patch    |  63 +++++
 .../recipes-httpd/nginx/nginx_1.24.0.bb       |   1 +
 13 files changed, 550 insertions(+), 1 deletion(-)
 rename meta-networking/recipes-daemons/postfix/{postfix_3.8.16.bb => postfix_3.8.17.bb} (99%)
 create mode 100644 meta-python/recipes-devtools/python/python3-grpcio/CVE-2024-7246.patch
 create mode 100644 meta-python/recipes-devtools/python/python3-tornado/CVE-2026-31958.patch
 create mode 100644 meta-webserver/recipes-httpd/nginx/nginx-1.24.0/CVE-2026-9256.patch

-- 
2.54.0



             reply	other threads:[~2026-06-09 12:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-09 12:49 Anuj Mittal [this message]
2026-06-16  8:13 ` [PATCH 00/13] Scarthgap pull request Anuj Mittal
2026-06-17  1:13 ` Khem Raj
  -- strict thread matches above, loose matches on Subject: below --
2025-12-22  6:52 Anuj Mittal
2025-12-22 15:03 ` Khem Raj

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=cover.1781009217.git.anuj.mittal@oss.qualcomm.com \
    --to=anuj.mittal@oss.qualcomm.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=raj.khem@gmail.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