docker-library / docker-library/mongo
Critical vulnerabilities on mongo linux amd64 image
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 1.1k
- Forks
- 658
- Avg merge
- 4h 40m
- Merged PRs (30d)
- 1
Description
Hi,
It seems your latest image has lot of vulnerabilities. Can you please update it to eliminate these?
{
"image": "library/mongo@sha256:4b5bf3c2bb7516164f6dcb44acce4fdcb428abfe5771a1128304a0f34ab9ff7c",
"severity": "CRITICAL",
"vulnerability_ids": ["CVE-2025-68121","CVE-2026-27143","GO-2026-4337-stdlib","GO-2026-5005-golang.org/x/crypto","GO-2026-5006-golang.org/x/crypto","GO-2026-5017-golang.org/x/crypto","GO-2026-5019-golang.org/x/crypto","GO-2026-5020-golang.org/x/crypto","GO-2026-5021-golang.org/x/crypto","GO-2026-5023-golang.org/x/crypto","GO-2026-5026-golang.org/x/net"]
},
Same is visible in the offiical repository
https://hub.docker.com/layers/library/mongo/7.0.34/images/sha256-f11d03e9d23a4fa6131dd6a840cb5fb6bbfb557861f9c20f4b5a501192ac1584
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported library/mongo image digest and the MongoDB 7.0.34 Docker Hub image, then review each listed critical vulnerability and its affected component. Verify the resulting linux amd64 image no longer reports those CVEs and Go advisories in the vulnerability scan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, linux, mongodb
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100