[BUG] CVE-2026-42055. When will there be 1.30.3+ or 1.31.2+ part of this image?

Open Beginner friendly
#616 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
docker, nginx
Domain
devops, security

Research direction

Start with the Docker image build configuration and identify where the nginx package or base image version is selected. Rebuild the swag image and run nginx -v inside the container; done means it reports nginx 1.30.3+ or 1.31.2+ and addresses CVE-2026-42055.

Written by the indexing model from the issue text.

Description

no-issue-activity
Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

Current swag images have nginx releases 1.28.x included which are effected by CVE-2026-42055. It takes at least nginx 1.30.3+ or 1.31.2+ to fix the issue.

Expected Behavior

swag images are being updated with nginx versions fixing CVE-2026-42055.

Steps To Reproduce
  1. Create swag container
  2. Execute nginx -v inside container
Environment
CPU architecture

x86-64

Docker creation
image: lscr.io/linuxserver/swag:latest
Container logs
nginx version: nginx/1.28.3
Dominant language
Dockerfile
Stars
3.7k
Forks
276
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linuxserver/docker-swag

All issues in linuxserver/docker-swag

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.