🚨 Security: Critical or high vulnerabilities in blender-mcp container
Open
Nobody has claimed this yet.
grype
high
security
- Dominant language
- Go
- Stars
- 8
- Forks
- 7
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 62
Description
🚨 Security Scan Alert
A periodic security scan found fixable critical or high severity vulnerabilities in the container image. Findings at this level also block publishing in the build workflow.
- Image:
ghcr.io/stacklok/dockyard/uvx/blender-mcp:1.5.6 - Critical vulnerabilities: 0
- High vulnerabilities: 1
Details
See the Security tab for full details.
High Vulnerabilities
- GHSA-8xx6-hgc6-gc2m in
httpx2@2.10.0: HTTPX2: Streaming response decompression does not bound peak memory (decompression amplification)
Automated security scan from periodic-security-scan workflow
Contributor guide
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 Security tab finding for GHSA-8xx6-hgc6-gc2m and trace how httpx2@2.10.0 enters the ghcr.io/stacklok/dockyard/uvx/blender-mcp:1.5.6 image. Check the periodic-security-scan and build workflows after the dependency or image is updated; done means the high vulnerability no longer appears and publishing is no longer blocked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100