Skip to content

Fixable CVEs in jellyfin/jellyfin (0 critical, 7 high) #990

Open

Description

@github-actions

The weekly CVE scan found fixable HIGH or CRITICAL vulnerabilities in jellyfin/jellyfin. 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.

jellyfin/jellyfin:12.4

Stacks: media. Digest: sha256:fea863d0cd9ec445985d9c75fc6ed64e38a1d2766cf0c250a33d553f4fc1b771.

Severity ID Package Installed Fixed in
HIGH CVE-2026-114146 Microsoft.AspNetCore.App.Runtime.linux-x64 10.0.14 8.0.34, 9.0.23, 10.0.15, 11.0.0
HIGH CVE-2026-114147 Microsoft.AspNetCore.App.Runtime.linux-x64 10.0.14 8.0.34, 9.0.23, 10.0.15, 11.0.0
HIGH CVE-2026-114149 Microsoft.AspNetCore.App.Runtime.linux-x64 10.0.14 8.0.34, 9.0.23, 10.0.15, 11.0.0
HIGH CVE-2026-109518 apt 3.0.3 3.0.4
HIGH CVE-2026-109518 libapt-pkg7.0 3.0.3 3.0.4
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
    mediastacks/media on smaug (VLAN 40)
    on Oct 7, 2026
  2. added a commit that references this issue on Oct 7, 2026
  3. changed the title [-]Fixable CVEs in jellyfin/jellyfin (3 critical, 17 high)[/-] [+]Fixable CVEs in jellyfin/jellyfin (0 critical, 1 high)[/+] on Oct 8, 2026
  4. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

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

    • The pinned digest sha256:357724bf… is the current jellyfin/jellyfin:12.2 / 12 / latest on Docker Hub (12.2.20261005-225228). Upstream hasn't published a newer build.
    • Debian released the fix, libpcre2-8-0 10.46-1~deb13u3 (DSA-6530-1), after that image was built, so no jellyfin image has it yet.
    • The risk in the meantime is low. Jellyfin is .NET with its own regex engine, and libpcre2 only comes along because the base image's tools depend on it.

    When upstream rebuilds 12.2.x (or ships 12.3), Dependabot should open the digest bump. Check it the way #1053 was checked, then deploy by hand on smaug. The next scan will then close this issue.

  5. Gerrrt commented on Oct 10, 2026

    @Gerrrt
    Owner

    Rechecked 2026-10-10. 12.2/12/latest still resolve to the pinned sha256:357724bf… (12.2.20261005-225228). There's no newer build, so this still waits.

    I checked the one path the note above didn't cover: jellyfin-ffmpeg, the component that parses untrusted media, doesn't link pcre2 either. On the pinned amd64 image:

    • ldd /usr/lib/jellyfin-ffmpeg/ffmpeg and …/ffprobe: no libpcre2.
    • No native library under /jellyfin or /usr/lib/jellyfin-ffmpeg links it.
    • The only package depending on libpcre2-8-0 is libselinux1.

    So CVE-2026-103111 isn't reachable from media files or from requests. The "low risk" above holds.

  6. changed the title [-]Fixable CVEs in jellyfin/jellyfin (0 critical, 1 high)[/-] [+]Fixable CVEs in jellyfin/jellyfin (2 critical, 22 high)[/+] on Oct 19, 2026
  7. changed the title [-]Fixable CVEs in jellyfin/jellyfin (2 critical, 22 high)[/-] [+]Fixable CVEs in jellyfin/jellyfin (2 critical, 23 high)[/+] on Oct 26, 2026
  8. github-actions commented on Oct 26, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-111497.

  9. changed the title [-]Fixable CVEs in jellyfin/jellyfin (2 critical, 23 high)[/-] [+]Fixable CVEs in jellyfin/jellyfin (3 critical, 22 high)[/+] on Nov 2, 2026
  10. changed the title [-]Fixable CVEs in jellyfin/jellyfin (3 critical, 22 high)[/-] [+]Fixable CVEs in jellyfin/jellyfin (0 critical, 4 high)[/+] on Nov 9, 2026
  11. github-actions commented on Nov 9, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-109518, CVE-2026-76844, CVE-2026-85091.

  12. Gerrrt commented on Nov 10, 2026

    @Gerrrt
    Owner

    Rechecked 2026-11-09 after #1288 moved the pin to 12.4. 12.4/12/latest still resolve to the pinned sha256:fea863d0… (12.4.20261026-211555). Only the nightly unstable tags are newer. Debian has both fixes (zlib 1:1.3.dfsg+really1.3.1-1+deb13u1 in DSA-6613-1, apt 3.0.4), but no jellyfin image includes them yet, so this still waits on an upstream rebuild.

    What's reachable, checked on the pinned amd64 image:

    • apt / libapt-pkg (CVE-2026-109518): only used at build time. Nothing at runtime calls it.
    • zlib (CVE-2026-76844, CVE-2026-85091): both bugs are in zlib's gzip file-writing path: gz_write() after a failed write(), and gz_vacate() from gzprintf() after a non-blocking stall. The parts that read media (inflate, PNG decoding, compressed streams) are separate code. CVE-2026-85091 also only affects 1.3.1.2+, and the image has 1.3.1.
    • Who links which zlib:
      • ffmpeg/ffprobe link a bundled /usr/lib/jellyfin-ffmpeg/lib/libz.so.1, not Debian's zlib1g. The scan can't see it, and Debian's fix won't change it. It's up to jellyfin-ffmpeg's own builds.
      • /jellyfin/libSkiaSharp.so is the only native library under /jellyfin that links the system libz.so.1. Skia decodes images, which uses inflate, not gzwrite.

    So neither zlib CVE can be reached from media files or requests. The risk stays low, same as the pcre2 round.

    How this closes doesn't change: when upstream rebuilds 12.4.x (or ships 12.5), Dependabot opens the digest bump. Check it the way #1053 and #1288 were checked, deploy by hand on smaug, and the next scan closes this issue.

  13. changed the title [-]Fixable CVEs in jellyfin/jellyfin (0 critical, 4 high)[/-] [+]Fixable CVEs in jellyfin/jellyfin (0 critical, 7 high)[/+] on Nov 16, 2026
  14. github-actions commented on Nov 16, 2026

    @github-actions
    Author

    New since the last scan: CVE-2026-114146, CVE-2026-114147, CVE-2026-114149.

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

    mediastacks/media on smaug (VLAN 40)securityA credential, an exposure, or a control that is weaker than recorded

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions