Skip to content

Fixable CVEs in sissbruecker/linkding (8 critical, 381 high) #1002

Open

Description

@github-actions

The weekly CVE scan found fixable HIGH or CRITICAL vulnerabilities in sissbruecker/linkding. This body is rewritten by every scan, and the issue closes itself when a scan finds the pinned digest clean.

The fix is normally the Dependabot bump for this image. If upstream has not released one, the fixed versions below say what to wait for.

sissbruecker/linkding:1.47.0

Stacks: sensitive. Digest: sha256:e35cb50e0581178f245125ffaa909c565416c94c9f22ace305a7d234a4345522.

Severity ID Package Installed Fixed in
CRITICAL CVE-2026-102268 PyJWT 2.13.0 2.14.0
CRITICAL GHSA-6q48-6c7w-9gw2 certifi 2025.11.12 2026.10.18
CRITICAL CVE-2026-111497 libbrotli1 1.1.0-2+b7 1.1.0-2+deb13u1
CRITICAL CVE-2026-98432 linux-libc-dev 6.12.101-1 6.12.113-1
CRITICAL CVE-2026-99083 linux-libc-dev 6.12.101-1 6.12.115-2
CRITICAL CVE-2026-13221 perl-base 5.40.1-6 5.40.1-6+deb13u1
CRITICAL CVE-2026-42496 perl-base 5.40.1-6 5.40.1-6+deb13u1
CRITICAL CVE-2026-8376 perl-base 5.40.1-6 5.40.1-6+deb13u1
HIGH CVE-2026-15307 Django 6.0.7 5.2.17, 6.0.8
HIGH CVE-2026-102266 PyJWT 2.13.0 2.14.0
HIGH CVE-2026-102267 PyJWT 2.13.0 2.14.0
HIGH CVE-2026-102271 PyJWT 2.13.0 2.14.0
HIGH CVE-2026-102272 PyJWT 2.13.0 2.14.0
HIGH CVE-2026-102273 PyJWT 2.13.0 2.14.0
HIGH GHSA-pxh4-856f-4h89 PyJWT 2.13.0 2.14.0
HIGH CVE-2026-109518 apt 3.0.3 3.0.4
HIGH CVE-2026-53612 bsdutils 1:2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53613 bsdutils 1:2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53614 bsdutils 1:2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53615 bsdutils 1:2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-8286 curl 8.14.1-2+deb13u4 8.14.1-2+deb13u7
HIGH CVE-2026-8927 curl 8.14.1-2+deb13u4 8.14.1-2+deb13u7
HIGH CVE-2026-92392 curl 8.14.1-2+deb13u4 8.14.1-2+deb13u7
HIGH CVE-2026-114136 djangorestframework 3.17.2 3.18.2
HIGH CVE-2026-114137 djangorestframework 3.17.2 3.18.2
HIGH CVE-2026-114138 djangorestframework 3.17.2 3.18.2
HIGH CVE-2026-41992 gzip 1.13-1 1.13-1+deb13u1
HIGH CVE-2026-109518 libapt-pkg7.0 3.0.3 3.0.4
HIGH CVE-2026-53612 libblkid1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53613 libblkid1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53614 libblkid1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53615 libblkid1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-4878 libcap2 1:2.75-10+b1 1:2.75-10+deb13u1
HIGH CVE-2026-8286 libcurl4t64 8.14.1-2+deb13u4 8.14.1-2+deb13u7
HIGH CVE-2026-8927 libcurl4t64 8.14.1-2+deb13u4 8.14.1-2+deb13u7
HIGH CVE-2026-92392 libcurl4t64 8.14.1-2+deb13u4 8.14.1-2+deb13u7
HIGH CVE-2026-53612 liblastlog2-2 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53613 liblastlog2-2 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53614 liblastlog2-2 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53615 liblastlog2-2 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53612 libmount1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53613 libmount1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53614 libmount1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53615 libmount1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-103111 libpcre2-8-0 10.46-1~deb13u1 10.46-1~deb13u3
HIGH CVE-2026-86145 libpcre2-8-0 10.46-1~deb13u1 10.46-1~deb13u2
HIGH CVE-2026-89157 libpcre2-8-0 10.46-1~deb13u1 10.46-1~deb13u2
HIGH CVE-2026-89161 libpcre2-8-0 10.46-1~deb13u1 10.46-1~deb13u2
HIGH CVE-2026-116304 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116306 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116307 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116309 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116314 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116315 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116316 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116317 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116319 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116320 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116323 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116325 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116326 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116328 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116330 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116331 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116332 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116335 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116336 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120139 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120141 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120142 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120143 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120145 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120147 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120148 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120149 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120150 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120151 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120153 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-14661 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-14662 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14664 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14668 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14669 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14670 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14671 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14677 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14679 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14680 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-15741 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-15742 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-16239 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-18408 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-18447 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-19385 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-6460 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-6464 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-6467 libpq-dev 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-6471 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-6473 libpq-dev 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-116304 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116306 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116307 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116309 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116314 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116315 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116316 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116317 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116319 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116320 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116323 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116325 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116326 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116328 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116330 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116331 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116332 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116335 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-116336 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120139 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120141 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120142 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120143 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120145 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120147 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120148 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120149 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120150 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120151 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-120153 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-14661 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-14662 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14664 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14668 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14669 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14670 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14671 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14677 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14679 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-14680 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-15741 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-15742 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-16239 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-18408 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-18447 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-19385 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-6460 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-6464 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-6467 libpq5 17.10-0+deb13u1 17.12-0+deb13u1
HIGH CVE-2026-6471 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-6473 libpq5 17.10-0+deb13u1 17.11-0+deb13u1
HIGH CVE-2026-53612 libsmartcols1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53613 libsmartcols1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53614 libsmartcols1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53615 libsmartcols1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-11822 libsqlite3-0 3.46.1-7 3.46.1-7+deb13u2
HIGH CVE-2026-11824 libsqlite3-0 3.46.1-7 3.46.1-7+deb13u2
HIGH CVE-2026-58050 libssh2-1t64 1.11.1-1+deb13u1 1.11.1-1+deb13u2
HIGH CVE-2026-14456 libssl-dev 3.5.6-1~deb13u2 3.5.7-1~deb13u2
HIGH CVE-2026-84782 libssl-dev 3.5.6-1~deb13u2 3.5.7-1~deb13u3
HIGH CVE-2026-14456 libssl3t64 3.5.6-1~deb13u2 3.5.7-1~deb13u2
HIGH CVE-2026-84782 libssl3t64 3.5.6-1~deb13u2 3.5.7-1~deb13u3
HIGH CVE-2026-53612 libuuid1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53613 libuuid1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53614 libuuid1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53615 libuuid1 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2025-22104 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2025-38137 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2025-38187 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2025-38204 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2025-38206 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2025-38421 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2025-38636 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2025-38656 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2025-39859 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2025-39862 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2025-39958 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2025-68174 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2025-68735 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-100072 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-23208 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-23327 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-31493 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-43185 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-43198 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-46130 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-46181 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-52991 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-53000 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-53089 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-53091 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-53109 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-53118 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-53277 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-53330 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-63879 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-64017 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-64283 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-64389 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-64400 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-68138 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-68159 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-68166 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-68264 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-68409 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-68426 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-68470 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-68480 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-72098 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-72463 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-74269 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-74469 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74476 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74480 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74488 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74509 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74516 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74518 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74520 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-74556 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74569 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74580 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74581 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74582 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74583 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74588 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74597 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74615 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74616 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74630 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74631 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74662 linux-libc-dev 6.12.101-1 6.12.107-1
HIGH CVE-2026-74669 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74705 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74743 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74744 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74746 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-74752 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-74753 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80521 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80522 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-80530 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-80586 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-80590 linux-libc-dev 6.12.101-1 6.12.107-1
HIGH CVE-2026-80714 linux-libc-dev 6.12.101-1 6.12.105-1
HIGH CVE-2026-80725 linux-libc-dev 6.12.101-1 6.12.107-1
HIGH CVE-2026-80780 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80792 linux-libc-dev 6.12.101-1 6.12.107-1
HIGH CVE-2026-80824 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80837 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80840 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80841 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80842 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80844 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80848 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80849 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80850 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80852 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80878 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80921 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80926 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-80951 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-81000 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-81003 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89465 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89479 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89481 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89487 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89488 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89508 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89524 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89526 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89530 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89536 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89545 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89563 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89564 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89569 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89607 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89617 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89631 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-89633 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-89638 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-89652 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89653 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89656 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89659 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89663 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89669 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89674 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89676 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89690 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89708 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89713 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89725 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89736 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89761 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89777 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89811 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-89846 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89894 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89932 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-89972 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-90011 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-90036 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-90049 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-90071 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-90111 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-90206 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-90227 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-90414 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-93207 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-93288 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-93817 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-97417 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-97564 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-98107 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-98110 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-98111 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-98116 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-98155 linux-libc-dev 6.12.101-1 6.12.111-1
HIGH CVE-2026-98171 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98222 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98232 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98275 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98323 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98378 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98417 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98442 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98466 linux-libc-dev 6.12.101-1 6.12.117-1
HIGH CVE-2026-98490 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98532 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98548 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98549 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98573 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98614 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98621 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98715 linux-libc-dev 6.12.101-1 6.12.117-1
HIGH CVE-2026-98716 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98725 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98741 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98742 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98769 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98805 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98853 linux-libc-dev 6.12.101-1 6.12.117-1
HIGH CVE-2026-98857 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98927 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-98974 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-99018 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-99056 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-99064 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-99109 linux-libc-dev 6.12.101-1 6.12.117-1
HIGH CVE-2026-99110 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-99152 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-99153 linux-libc-dev 6.12.101-1 6.12.115-2
HIGH CVE-2026-99227 linux-libc-dev 6.12.101-1 6.12.115-1
HIGH CVE-2026-99231 linux-libc-dev 6.12.101-1 6.12.115-1
HIGH CVE-2026-99233 linux-libc-dev 6.12.101-1 6.12.115-1
HIGH CVE-2026-99236 linux-libc-dev 6.12.101-1 6.12.115-1
HIGH CVE-2026-99246 linux-libc-dev 6.12.101-1 6.12.115-1
HIGH CVE-2026-99281 linux-libc-dev 6.12.101-1 6.12.117-1
HIGH CVE-2026-99284 linux-libc-dev 6.12.101-1 6.12.115-1
HIGH CVE-2026-99288 linux-libc-dev 6.12.101-1 6.12.117-1
HIGH CVE-2026-99999 linux-libc-dev 6.12.101-1 6.12.113-1
HIGH CVE-2026-53612 login 1:4.16.0-2+really2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53613 login 1:4.16.0-2+really2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53614 login 1:4.16.0-2+really2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53615 login 1:4.16.0-2+really2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53612 mount 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53613 mount 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53614 mount 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53615 mount 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-14456 openssl 3.5.6-1~deb13u2 3.5.7-1~deb13u2
HIGH CVE-2026-84782 openssl 3.5.6-1~deb13u2 3.5.7-1~deb13u3
HIGH CVE-2026-14456 openssl-provider-legacy 3.5.6-1~deb13u2 3.5.7-1~deb13u2
HIGH CVE-2026-84782 openssl-provider-legacy 3.5.6-1~deb13u2 3.5.7-1~deb13u3
HIGH CVE-2026-42497 perl-base 5.40.1-6 5.40.1-6+deb13u1
HIGH CVE-2026-48962 perl-base 5.40.1-6 5.40.1-6+deb13u1
HIGH CVE-2026-57432 perl-base 5.40.1-6 5.40.1-6+deb13u1
HIGH CVE-2026-57433 perl-base 5.40.1-6 5.40.1-6+deb13u1
HIGH CVE-2026-126190 soupsieve 2.8.4 4.0.0
HIGH CVE-2026-126191 soupsieve 2.8.4 3.0.2
HIGH CVE-2026-97687 urllib3 2.7.0 2.8.0
HIGH CVE-2026-97689 urllib3 2.7.0 2.8.0
HIGH CVE-2026-53612 util-linux 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53613 util-linux 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53614 util-linux 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-53615 util-linux 2.41-5 2.41.5-0+deb13u1
HIGH CVE-2026-76844 zlib1g 1:1.3.dfsg+really1.3.1-1+b1 1:1.3.dfsg+really1.3.1-1+deb13u1
HIGH CVE-2026-85091 zlib1g 1:1.3.dfsg+really1.3.1-1+b1 1:1.3.dfsg+really1.3.1-1+deb13u1

Written by .github/workflows/cve-scan.yml in this run.

Activity

  1. added
    securityA credential, an exposure, or a control that is weaker than recorded
    sensitivestacks/sensitive on trinity (VLAN 99)
    on Oct 7, 2026
  2. github-actions commented on Oct 10, 2026

    @github-actions
    Author
  3. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Triage, 2026-10-10: waiting on upstream. Nothing to change here.

    • The pin is current. 1.47.0 (2026-09-13) is linkding's latest release, and :1.47.0 and :latest both resolve to the pinned sha256:e35cb50e…. The tag hasn't been rebuilt, so Dependabot has nothing to bump. (-plus is a different digest, with the same base and an added Chromium. It's not a way out.)
    • Upstream has the Python fixes waiting, but hasn't merged them. Its Dependabot opened Bump pyjwt from 2.13.0 to 2.15.0 sissbruecker/linkding#1505 (PyJWT 2.15.0), Bump urllib3 from 2.7.0 to 2.8.0 sissbruecker/linkding#1504 (urllib3 2.8.0) and Bump django from 6.0.7 to 6.0.8 sissbruecker/linkding#1503 (Django 6.0.8) on 2026-10-01. All three are still open, and main hasn't moved since the 1.47.0 release. The Debian findings come from the python:3.13.7-slim-trixie base, and they clear only when upstream rebuilds on a newer base.
    • What to wait for: a linkding release after 1.47.0. Its Dependabot PR on stacks/sensitive (Sundays) gets merged, homelab-converge-sensitive deploys it within the hour (Nothing converges stacks/sensitive: the tier with the real data is the only one deployed by hand #533), and the next scan closes this issue if the new digest is clean.
    • Most of the 195 findings, including the 4 critical, aren't on a path this deployment uses:
      • PyJWT (1 critical, 5 high) is pulled in only by mozilla-django-oidc, and linkding loads that only when LD_ENABLE_OIDC is set. We don't set it.
      • libpq5 / libpq-dev (34) are the Postgres client libraries. linkding uses them only with LD_DB_ENGINE=postgres, and this deployment uses SQLite.
      • linux-libc-dev (105) is kernel headers for compiling. The container runs on trinity's kernel, not these.
      • perl-base (3 critical, 1 high) is in the Debian base image. linkding is Django under uwsgi, so nothing in its request path runs Perl.
      • What's left and reachable: Django 6.0.7 and urllib3 (adding a bookmark fetches the page's title and description from the site), plus openssl, sqlite and pcre2 in the base image.
    • Exposure while we wait: linkding has no published port and is reachable only through Caddy at links.matrix.elysium, by the household. Request handlers run as www-data with no effective capabilities, on a read-only root filesystem. Background tasks are off, so linkding doesn't fetch favicons or previews. We're not building and patching our own image. We take upstream's release instead.
  4. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    This is waiting on upstream. Nothing in the repo needs to change.

    • The pinned digest is current: sissbruecker/linkding:1.47.0 (sha256:e35cb50e…). pin-digests.sh reports no drift, so the tag hasn't been rebuilt since it was pinned.
    • There is no newer release on the registry to move to.
    • The fixed versions exist (table above), but no published image includes them yet. Mostly:
      • linux-libc-dev: 105 findings, fixed in 3 different versions (see the table)
      • libpq-dev: 17 findings, fixed in 17.11-0+deb13u1
      • libpq5: 17 findings, fixed in 17.11-0+deb13u1
      • perl-base: 7 findings, fixed in 5.40.1-6+deb13u1
      • PyJWT: 6 findings, fixed in 2.14.0
      • libpcre2-8-0: 4 findings, fixed in 2 different versions (see the table)
      • and 43 more across 19 other packages

    When upstream rebuilds or ships a release with these fixes, Dependabot should open the bump. Check it with trivy and check_image_pins.py, then deploy. The next scan will then close this issue.

  5. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Checked 2026-10-10: switching to 1.47.0-alpine is not a way out either, unlike immich-valkey (#1006 → #1147).

    trivy 0.75.0, with scan-images.sh's flags (--image-src remote --platform linux/amd64 --scanners vuln --severity HIGH,CRITICAL --ignore-unfixed):

    Debian 1.47.0 (pinned, e35cb50e…) Alpine 1.47.0-alpine (04e67acd…)
    Total 4 critical, 195 high 3 critical, 51 high
    OpenSSL 3.5.6, 8 high 3.5.1, 2 critical + 16 high
    PyJWT / Django / urllib3 same same (Python deps are identical)
    libpq 34 18
    linux-libc-dev, perl-base, util-linux 105 + 7 + ~30 none

    The count drops because the Alpine image doesn't carry kernel headers, Perl or util-linux, and none of those is on linkding's request path anyway. What the Alpine variant adds is an older OpenSSL (3.5.1) with two criticals, and OpenSSL is on a reachable path: urllib3's TLS when adding a bookmark fetches the target page. It would also mean a variant change for uwsgi/www-data on a stateful service, for no gain in what can be reached.

    Upstream is unchanged: 1.47.0 is still the latest, and sissbruecker/linkding#1503 (Django 6.0.8), sissbruecker/linkding#1504 (urllib3 2.8.0) and sissbruecker/linkding#1505 (PyJWT 2.15.0) are all still open. This keeps waiting on the next release.

    🤖 Generated with Claude Code

  6. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Rechecked 2026-10-10. Upstream is unchanged: 1.47.0 is still the latest, and #1503–#1505 are still open. But I found a root cause the triage above didn't name: upstream builds on a Python patch tag that's a year stale.

    Both stages of linkding's docker/default.Dockerfile are FROM python:3.13.7-slim-trixie. Docker's official images only rebuild the current patch tag, so that tag was last pushed 2025-10-02. linkding's .github/dependabot.yml covers only npm in /docs. Nothing bumps the FROM lines or the pip requirements on a schedule, which is why the Debian layer never moves. It's the same pattern as docker-socket-proxy's frozen HAProxy base (#1005).

    The two bases on their own, with trivy 0.75.0 and scan-images.sh's flags:

    Base Pushed Fixable HIGH/CRITICAL
    python:3.13.7-slim-trixie (what linkding uses) 2025-10-02 6 critical, 66 high: openssl/libssl3t64/legacy provider ×30, perl-base ×7, util-linux family ×21, pcre2 ×4, sqlite ×2, gzip, libcap2
    python:3.13-slim-trixie (current) 2026-10-09 0 OS findings. 4 high in the base's own bundled pip packages (msgpack, setuptools, urllib3).

    So a rebuild on the current python:3.13-slim-trixie would clear the perl-base criticals and every base-layer row, with no code change. The Dockerfile's own apt-get install packages (libpq5/libpq-dev, linux-libc-dev) were resolved when 1.47.0 was built on 2026-09-13. A fresh build pulls today's trixie-security versions of those too. What a rebuild alone wouldn't clear is the Python dependencies: PyJWT, Django and urllib3 still need #1503–#1505 merged.

    That makes this worth raising upstream. Asking for a release only clears the findings if it's built on a current base, and nothing upstream keeps the base current.

  7. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Upstream report: sissbruecker/linkding#1518 (the frozen python:3.13.7 base in both Dockerfiles, and no Dependabot coverage for Docker or pip).

  8. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    The criticals, traced against the live container, 2026-10-10

    This is the same trace as on #979, #1003, #1004 and #1009 to #1011. I took each advisory's precondition and checked it against the running sensitive-linkding on trinity (linkding:1.47.0@sha256:e35cb50e…); a fresh trivy 0.75.0 scan matches the body. The 4 criticals are 3 in perl-base and 1 in PyJWT. None is reachable.

    CVE Package What the bug needs What the live container does Reachable?
    CVE-2026-13221 perl-base 5.40.1 Perl compiling a regex alternation of more than 65535 fixed branches Perl never runs. The container's processes are docker-init → bootstrap.sh and four uwsgi --http [::]:9090 workers (Django). /usr/bin/perl is on disk only because Debian marks perl-base essential. No
    CVE-2026-8376 perl-base 5.40.1 Perl compiling an attacker-controlled regex on a 32-bit build The same: Perl never runs, and the container is x86_64 anyway. No
    CVE-2026-42496 perl-base 5.40.1 (Archive::Tar) Perl's Archive::Tar extracting an attacker-supplied tarball Archive/Tar.pm isn't in the image at all (it ships in perl-modules, which isn't installed), so the vulnerable code is absent. trivy flags it through the shared source package. No
    CVE-2026-102268 PyJWT 2.13.0 An app accepting both HMAC and asymmetric algorithms with one key The only importer of jwt in the venv is mozilla_django_oidc/auth.py, and only mozilla-django-oidc declares PyJWT. linkding loads that module only through AUTHENTICATION_BACKENDS under if LD_ENABLE_OIDC: (bookmarks/settings/base.py:214), and adds the oidc/ routes under the same flag (bookmarks/urls.py:153). LD_ENABLE_OIDC isn't set in the container. Even with OIDC on, auth.py:135 rejects any token whose alg isn't the single OIDC_RP_SIGN_ALGO, so HMAC and asymmetric never mix. No

    (mozilla_django_oidc is in INSTALLED_APPS unconditionally, but registering the app doesn't import auth.py.)

    This confirms the triage above ("PyJWT … only when LD_ENABLE_OIDC is set", "nothing in its request path runs Perl"), now checked against the running container rather than inferred. That triage already names what is reachable: Django and urllib3 (HIGHs), plus openssl, sqlite and pcre2. This trace doesn't cover those.

    What would change this:

    • Setting LD_ENABLE_OIDC, which loads PyJWT but still isn't vulnerable while OIDC_RP_SIGN_ALGO is a single asymmetric algorithm.
    • A linkding release that runs Perl or installs perl-modules.

    To reproduce:

    docker exec sensitive-linkding sh -c 'uname -m; for p in /proc/[0-9]*; do tr "\0" " " < $p/cmdline; echo; done | sort -u; find / -xdev -path "*Archive/Tar.pm"; env | grep LD_ENABLE_OIDC; grep -rlE "^\s*(import jwt|from jwt)" /etc/linkding/.venv/lib/python3.13/site-packages --include=*.py | grep -v /jwt/'

    🤖 Traced by Claude Code

  9. Gerrrt commented on Oct 11, 2026

    @Gerrrt
    Owner

    The HIGHs, traced against the live container, 2026-10-11: one is reachable through any bookmarked site

    This follows the criticals trace above, against the running sensitive-linkding on trinity (still 1.47.0@sha256:e35cb50e…). A fresh trivy 0.75.0 scan gives 195 HIGH rows, 148 distinct CVEs. One is reachable: urllib3 CVE-2026-97689, a memory-exhaustion DoS triggered by a hostile web server when linkding fetches a bookmarked page. None of the others is.

    Reachable: urllib3 2.7.0, CVE-2026-97689 (fixed in 2.8.0)

    The bug: HTTPResponse.read_chunked/stream buffers a chunked response's chunk-size line until newline or EOF with no length bound, so a server that sends Transfer-Encoding: chunked and then an endless size line grows the client's memory without limit.

    The path: bookmarks/services/website_loader.py load_page() does http_client.get(url, timeout=10, headers=…, stream=True) and then for chunk in r.iter_content(…), which is exactly the stream → read_chunked path. load_website_metadata() calls it, and it runs when a bookmark is added and from the API's check route (bookmarks/api/routes.py:113). linkding's guards don't cover it:

    • MAX_CONTENT_LIMIT (5000 KiB) counts decoded body bytes, and the size line is never body.
    • timeout=10 is per socket read, so a server that keeps sending never trips it.
    • uwsgi's harakiri is set only if-env LD_REQUEST_TIMEOUT, which isn't set.
    • LD_DISABLE_BACKGROUND_TASKS=True stops favicon and preview fetches, but not this title/description fetch.

    Who can trigger it: any logged-in linkding user. More to the point, any website a household member bookmarks: the page's own server answers linkding's fetch, so the attacker needs no account, only a bookmark of their URL. This is from the code path; I didn't exercise it.

    Impact: a uwsgi worker grows until the container's 512 MiB mem_limit OOM-kills it, and restart: unless-stopped brings it back. It takes two processes × two threads, so it's an outage of linkding, not of trinity. No data is read.

    Upstream: sissbruecker/linkding#1504 (urllib3 2.8.0) is still open, there's no release after 1.47.0, and our report sissbruecker/linkding#1518 has no reply.

    Not reachable

    Package (distinct CVEs) Why
    linux-libc-dev (105) Kernel headers for compiling. The container runs trinity's kernel.
    libpq5, libpq-dev (17 each) The Postgres client. LD_DB_ENGINE is unset, so linkding uses SQLite.
    PyJWT (5) Only via mozilla_django_oidc/auth.py, which loads only if LD_ENABLE_OIDC, and that isn't set (traced in the criticals comment).
    Django 6.0.7, CVE-2026-15307 GeoDjango spatial lookups only. django.contrib.gis isn't in linkding's settings.
    libsqlite3-0 (2), FTS5 Both need a crafted database file with malformed FTS5 pages. linkding opens only its own /etc/linkding/data/db.sqlite3, and its imports are Netscape HTML, not database files.
    libpcre2-8-0 (4) Each needs an attacker-controlled pattern (103111, 86145), a 32-bit build (89157), or JIT with a copied subject (89161). Python's re isn't PCRE. uwsgi's PCRE use, if any, is config routes, not request input.
    openssl, libssl3t64, libssl-dev, openssl-provider-legacy (2) QUIC server (14456) and DTLS (84782). Python's ssl is a TLS client here.
    libssh2-1t64 (1) 32-bit only, plus a hostile SSH server. Nothing here speaks SSH.
    util-linux family: bsdutils, libblkid1, libmount1, libsmartcols1, libuuid1, liblastlog2-2, login, mount, util-linux (3 each) mount(8) SUID and fstab TOCTOU, needing a local user. The container runs uwsgi only, with no-new-privileges.
    libcap2 (1), gzip (1) Local cap_set_file TOCTOU / the gzip CLI's LZH path, which nothing runs.
    perl-base (4) Perl never runs (criticals comment).

    Limit of this trace: I couldn't read the uwsgi workers' /proc/<pid>/maps. They run as www-data, non-dumpable, under cap_drop: ALL, so which shared libraries they map is inferred from the code, not observed. None of the verdicts above depends on that.

    What would change this: urllib3 2.8.0 in a linkding release (the fix); LD_ENABLE_OIDC (PyJWT); LD_DB_ENGINE=postgres (libpq); or a linkding feature that imports database files.

    Possible mitigations while waiting (not taken):

    • Setting LD_REQUEST_TIMEOUT turns on uwsgi harakiri, which kills a request stuck in the fetch after N seconds. That bounds the duration, but not necessarily the memory, since a fast server can exceed 512 MiB within seconds.
    • Linkding's URL validation doesn't help, because the hostile server is a legitimate public site.

    To reproduce:

    docker exec sensitive-linkding sh -c 'sed -n 97,120p /etc/linkding/bookmarks/services/website_loader.py; env | grep -E "^LD_(DB_ENGINE|ENABLE_OIDC|REQUEST_TIMEOUT|DISABLE_BACKGROUND_TASKS)"; grep -n harakiri /etc/linkding/uwsgi.ini'

    🤖 Traced by Claude Code

  10. Gerrrt commented on Oct 11, 2026

    @Gerrrt
    Owner

    Decision on the 13:27 trace's mitigation: don't set LD_REQUEST_TIMEOUT. Wait for urllib3 2.8.0.

    From the running container's /etc/linkding/uwsgi.ini, the variable sets three things, not just harakiri:

    if-env = LD_REQUEST_TIMEOUT
    http-timeout = %(_)
    socket-timeout = %(_)
    harakiri = %(_)
    endif =
    • It wouldn't stop CVE-2026-97689. urllib3 2.7.0 reads the chunk-size line with no bound, so memory grows as fast as the hostile server can push bytes into trinity. At household WAN speeds (a few hundred Mbit/s to 1 Gbit/s), 512 MiB arrives in roughly 4–15 s. That's below any harakiri value that leaves room for normal requests (load_page alone allows 10 s per read). It would only bound a slow drip, which wouldn't reach mem_limit anyway. This estimate is from the code and link speeds; I didn't measure WAN throughput or exercise the path.
    • It would cost something. The same block shortens uwsgi's HTTP and socket timeouts for every request, including long Netscape-HTML imports and exports.

    So the exposure stays as the trace describes: a bookmarked hostile site can OOM-kill linkding's workers, the container restarts, and no data is read. The fix is sissbruecker/linkding#1504 (urllib3 2.8.0) in a release, ideally built on a current base (sissbruecker/linkding#1518). No change to stacks/sensitive/compose.yaml.

  11. changed the title [-]Fixable CVEs in sissbruecker/linkding (4 critical, 195 high)[/-] [+]Fixable CVEs in sissbruecker/linkding (4 critical, 231 high)[/+] on Oct 19, 2026
  12. changed the title [-]Fixable CVEs in sissbruecker/linkding (4 critical, 231 high)[/-] [+]Fixable CVEs in sissbruecker/linkding (9 critical, 279 high)[/+] on Oct 26, 2026
  13. changed the title [-]Fixable CVEs in sissbruecker/linkding (9 critical, 279 high)[/-] [+]Fixable CVEs in sissbruecker/linkding (7 critical, 259 high)[/+] on Nov 2, 2026
  14. github-actions commented on Nov 2, 2026

    @github-actions
    Author
  15. changed the title [-]Fixable CVEs in sissbruecker/linkding (7 critical, 259 high)[/-] [+]Fixable CVEs in sissbruecker/linkding (8 critical, 311 high)[/+] on Nov 9, 2026
  16. changed the title [-]Fixable CVEs in sissbruecker/linkding (8 critical, 311 high)[/-] [+]Fixable CVEs in sissbruecker/linkding (8 critical, 381 high)[/+] on Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    securityA credential, an exposure, or a control that is weaker than recordedsensitivestacks/sensitive on trinity (VLAN 99)

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions