Addressing security vulnerabilities in the Temporalio/ui:2.43.2
Open
Nobody has claimed this yet.
bug
- Dominant language
- TypeScript
- Stars
- 431
- Forks
- 179
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 71
Description
Expected Behavior
No more CVEs found
Actual Behavior
There are some CVEs found from the latest Temporal image:
temporalio/ui:2.43.2
Steps to Reproduce the Problem
Pull the latest image temporalio/ui:2.43.2 from Dockerhub
Scan the image with any vulnerability scanner
| CVE | SEVERITY | CVSS | PACKAGE | VERSION | FIX IN |
|---|---|---|---|---|---|
| CVE-2025-22870, CWE-918 | HIGH | 8.8 | golang.org/x/net/http/httpproxy | v0.34.0 | 0.36.0 |
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 by examining the temporalio/ui:2.43.2 Docker image and the golang.org/x/net/http/httpproxy dependency reported by the vulnerability scan. Reproduce the scan against the image, then verify that the dependency is fixed to version 0.36.0 or later and that no CVEs remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100