Skip to content

Free, Open Source, Self-Hosted WhatsApp API Gateway

ci(release): stop the image scan failing on the fixed arm64 Chromium

Yudhi Armyndharisfa9874d18197
diff --git a/.trivyignore b/.trivyignore
index b79827e20..aec8fcdd9 100644
--- a/.trivyignore
+++ b/.trivyignore
@@ -32,7 +32,7 @@ CVE-2026-102278
# entry once npm ships a bundle with undici >= 6.28.1.
CVE-2026-19534
-# Chromium: no entry, and the two architectures are not scanned alike.
+# Chromium: no accepted advisory, and the two architectures are not scanned alike.
#
# arm64 installs Debian's `chromium` and `chromium-sandbox` (Dockerfile, TARGETARCH branch) by choice;
# Chrome for Testing publishes linux-arm64 builds only from 153 on, and the image has not moved arm64 to
@@ -53,3 +53,31 @@ CVE-2026-19534
# lockfile names it, so neither the OS nor the library scanner can see it: a clean amd64 scan says
# nothing about the browser. Its version is the pin in the Dockerfile, and no scan will flag that pin
# as outdated.
+
+# CVE-2026-95282, CVE-2026-95293, CVE-2026-95301, CVE-2026-95304, CVE-2026-95306, CVE-2026-95315,
+# CVE-2026-95324, CVE-2026-95333, CVE-2026-95347, CVE-2026-95351, CVE-2026-95354, CVE-2026-95355,
+# CVE-2026-95373 and CVE-2026-95380: Chromium advisories fixed upstream in 154.0.8037.57. Every one is
+# published as affecting Chrome "prior to 154.0.8037.57".
+#
+# These accept nothing the image is exposed to. arm64 installs Debian's bookworm rebuild of that same
+# release, 154.0.8037.57-1~deb12u1, so it carries the fixes. Debian records the fix only against the
+# unstable build 154.0.8037.57-1 (DSA-6513-1 covers trixie), and `~deb12u1` sorts below `-1`, so the
+# scanner reports the bookworm rebuild as unfixed.
+#
+# Drop all fourteen once bookworm-security publishes the 154.0.8037.92-1~deb12u1 binaries the Debian
+# tracker already lists as its version (checked 2026-10-01, when the archive still served
+# 154.0.8037.57-1~deb12u1). The next image installs it, and it sorts above the recorded fix.
+CVE-2026-95282
+CVE-2026-95293
+CVE-2026-95301
+CVE-2026-95304
+CVE-2026-95306
+CVE-2026-95315
+CVE-2026-95324
+CVE-2026-95333
+CVE-2026-95347
+CVE-2026-95351
+CVE-2026-95354
+CVE-2026-95355
+CVE-2026-95373
+CVE-2026-95380
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 33d2379a2..548e2d927 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -404,6 +404,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
- The compose `minio` service no longer starts when no S3 secret is set, instead of starting with the server's default credentials.
- The MinIO container that Dashboard > Infrastructure creates for built-in storage no longer publishes ports 9000 and 9001 on the host's `127.0.0.1`; OpenWA reaches it over the Docker network.
- Release images on GHCR and Docker Hub carry a signed build provenance attestation from the release workflow; verify one with `gh attestation verify oci://ghcr.io/rmyndharis/openwa:<version> --repo rmyndharis/OpenWA --signer-workflow rmyndharis/OpenWA/.github/workflows/release.yml --source-ref refs/tags/v<version>`.
+- `linux/arm64` image: the release image scan no longer fails on 14 Chromium CVEs fixed upstream in 154.0.8037.57, which the image already runs as Debian's `154.0.8037.57-1~deb12u1` rebuild that the scanner ranks below the recorded fix. They are listed in `.trivyignore` until bookworm-security publishes a newer build.
- whatsapp-web.js: a session whose stored proxy URL is not a supported `http`, `https`, `socks4` or `socks5` URL ends `failed` with the fix named, instead of starting without the proxy.
- Baileys: unlinking a session no longer lets an in-flight chat-state write list the old account's chats, with their pin, mute or archive state, under the next linked account.
- Deleting a session while one of its bulk batches runs no longer brings the batch row, with its recipients and texts, back as `CANCELLED`.