Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

CVE-2025-26042 Still Listed as Open on Docker Scout Despite Being Fixed

Open
#200 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
docker
Domain
security

Research direction

Start by comparing Docker Scout's displayed entry for CVE-2025-26042 with the current GitHub advisory GHSA-hx7h-9vf7-5xhg and its withdrawn duplicate. Trace the vulnerability data or update entry point used by Docker Scout; done when Scout shows the corrected fixed or patched status and version.

Written by the indexing model from the issue text.

Description

I would like to report an issue where CVE-2025-26042 is still marked as open/vulnerable on Docker Scout, even though this CVE has already been fixed.

Background

There were previously duplicate advisories for this vulnerability:

  • GitHub Advisory:
    GHSA-hx7h-9vf7-5xhg (current and authoritative, shows the issue as fixed)

  • Withdrawn GitHub Advisory:
    GHSA-3rw8-4xrq-3f7p (withdrawn as a duplicate of the above)

  • NIST & GitLab Advisories:

    • Both still reference CVE-2025-26042, but do not reflect the current fixed status like GitHub does.
Request

Please update the status of CVE-2025-26042 on Docker Scout and display the correct fixed/patched version in accordance with the GitHub advisory (GHSA-hx7h-9vf7-5xhg).

If further details or context are needed, please let me know!

Thank you!

Dominant language
Shell
Stars
455
Forks
134
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 docker/scout-cli

All issues in docker/scout-cli

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.