From: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
To: buildroot@buildroot.org
Cc: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
Subject: [Buildroot] [PATCH v2] package/nginx: security bump to version 1.28.3
Date: Thu, 30 Apr 2026 11:10:32 +0530 [thread overview]
Message-ID: <20260430054033.8599-1-chakrabortyshubham66@gmail.com> (raw)
In-Reply-To: <20260429170808.1144652-1-chakrabortyshubham66@gmail.com>
Fixes the following security issues:
- CVE-2026-27654: Buffer overflow in ngx_http_dav_module when using the
alias directive with WebDAV COPY or MOVE requests.
- CVE-2026-27784 & CVE-2026-32647: Buffer overflows in ngx_http_mp4_module
when processing specially crafted MP4 files.
- CVE-2026-27651: NULL pointer dereference in the mail proxy module
during CRAM-MD5 or APOP authentication retries.
- CVE-2026-28753: DNS PTR record manipulation in auth_http or SMTP proxy.
- CVE-2026-28755: OCSP certificate check bypass in the stream module.
For a full list of changes, see:
https://nginx.org/en/CHANGES-1.28
---
v1 -> v2:
- Bump to 1.28.3 (stable) instead of 1.29.7 (mainline) as requested
by Marcus Hoffmann.
- Highlight security fixes in the commit message.
Signed-off-by: Shubham Chakraborty <chakrabortyshubham66@gmail.com>
---
package/nginx/nginx.hash | 2 +-
package/nginx/nginx.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/nginx/nginx.hash b/package/nginx/nginx.hash
index 7b79036b20..1d11937987 100644
--- a/package/nginx/nginx.hash
+++ b/package/nginx/nginx.hash
@@ -1,4 +1,4 @@
# Locally calculated after checking pgp signature
-sha256 40e7a0916d121e8905ef50f2a738b675599e42b2224a582dd938603fed15788e nginx-1.28.1.tar.gz
+sha256 2c96a946bfb0882a21744ed429770a2123ae1828c7c48665092993ddee91a918 nginx-1.28.3.tar.gz
# License files, locally calculated
sha256 77c01620abf36ed747b7eca4bd271e49023fe3a8e2b3525bcf4b09c8e3aa28e4 LICENSE
diff --git a/package/nginx/nginx.mk b/package/nginx/nginx.mk
index 41490caee2..a8b7ee7319 100644
--- a/package/nginx/nginx.mk
+++ b/package/nginx/nginx.mk
@@ -4,7 +4,7 @@
#
################################################################################
-NGINX_VERSION = 1.28.1
+NGINX_VERSION = 1.28.3
NGINX_SITE = https://nginx.org/download
NGINX_LICENSE = BSD-2-Clause
NGINX_LICENSE_FILES = LICENSE
--
2.54.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-04-30 5:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-18 7:33 [Buildroot] [PATCH] package/psmisc: bump to version 23.7 Shubham Chakraborty
2026-04-24 20:08 ` Julien Olivain via buildroot
2026-04-28 20:45 ` [Buildroot] [PATCH v2] " Shubham Chakraborty
2026-04-29 8:23 ` Marcus Hoffmann via buildroot
2026-04-29 13:06 ` [Buildroot] [PATCH v3] " Shubham Chakraborty
2026-04-29 22:31 ` Marcus Hoffmann via buildroot
2026-04-29 17:08 ` [Buildroot] [PATCH] package/nginx: bump to version 1.29.7 Shubham Chakraborty
2026-04-29 18:49 ` Marcus Hoffmann via buildroot
2026-04-29 18:52 ` Shubham Chakraborty
2026-04-30 5:40 ` Shubham Chakraborty [this message]
2026-05-04 8:31 ` [Buildroot] [PATCH v2] package/nginx: security bump to version 1.28.3 Marcus Hoffmann via buildroot
2026-05-04 9:43 ` Shubham Chakraborty
2026-05-15 13:34 ` Thomas Perale via buildroot
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=20260430054033.8599-1-chakrabortyshubham66@gmail.com \
--to=chakrabortyshubham66@gmail.com \
--cc=buildroot@buildroot.org \
/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