Skip to content

chore(deps): update docker-sbx to v0.26.1#20913

Merged
github-actions[bot] merged 1 commit intomainfrom
renovate/docker-sbx-0.x
Apr 17, 2026
Merged

chore(deps): update docker-sbx to v0.26.1#20913
github-actions[bot] merged 1 commit intomainfrom
renovate/docker-sbx-0.x

Conversation

@uniget-bot
Copy link
Copy Markdown

@uniget-bot uniget-bot commented Apr 17, 2026

This PR contains the following updates:

Package Update Change
docker-sbx minor 0.25.0 → 0.26.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

docker/sbx-releases (docker-sbx)

v0.26.1

Compare Source

Highlights

This release introduces sbx diagnose, a new command for gathering and uploading diagnostic information when troubleshooting sandbox issues. Factory.ai joins the roster of supported agents with a dedicated template. Agents that use OAuth flows now benefit from an xdg-open shim and localhost OAuth callback, enabling browser-based auth redirects to work seamlessly inside sandboxes. Template management is expanded with sbx template save, load, ls, and rm commands, plus a warning when loading a template built for a different agent. The daemon now supports log rotation and improved logging in foreground and debug modes.

On the networking front, Claude's download domains (downloads.claude.ai, claude.com) are now on the default proxy allow list, and domain-allow rules now correctly override implicit CIDR denies for IP literals.

What's New

CLI
  • Warn when a template was built for a different agent (#​2241)
Daemon
  • Add log rotation for daemon logs (#​2307)
  • Fix daemon logging in foreground and debug modes (#​2328)
Templates
  • Add sbx template save, load, ls, and rm commands (#​2317)
Networking
  • Add downloads.claude.ai and claude.com to Claude's proxy allow list (#​2336)
  • Domain-allow rules now override implicit CIDR deny for IP address literals (#​2329)
  • Add **.hashicorp.com to the default allow list (#​2291)
Diagnose
  • Add sbx diagnose command for collecting and uploading diagnostic data (#​2332)
Agents
  • Add support for Factory.ai (#​2249)
  • Add xdg-open shim and localhost callback to support OAuth redirects inside sandboxes (#​2260)
Bug Fixes
  • Fix stopped sandbox disappearing from list when a prefix-named sandbox is running (#​2313)
  • Fix new session being killed by an in-progress auto-stop (#​2278)
  • Fix exec "command not found" detection from stdout and stderr (#​2300)
  • Fix Ghostty launch on macOS to use file-based launch (#​2296)
  • Detect terminal background color instead of system appearance (#​2299)
  • Improve accuracy and detail of policy denial log messages (#​2281)

Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

nicholasdille-bot
nicholasdille-bot approved these changes Apr 17, 2026
View reviewed changes
Copy link
Copy Markdown

@nicholasdille-bot nicholasdille-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved because label type/renovate is present.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 17, 2026

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/docker-sbx:0.26.1

📦 Image Reference ghcr.io/uniget-org/tools/docker-sbx:0.26.1
digestsha256:81b714c075e3830d8b7eb38c3bff01d43b94d70e6bb6ae772155298b72532aad
vulnerabilitiescritical: 0 high: 2 medium: 4 low: 3
platformlinux/amd64
size68 MB
packages311
critical: 0 high: 2 medium: 0 low: 0 github.com/moby/buildkit 0.26.3 (golang)

pkg:golang/github.com/moby/buildkit@0.26.3

high 8.4: CVE--2026--33747 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range<0.28.1
Fixed version0.28.1
CVSS Score8.4
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score0.055%
EPSS Percentile17th percentile
Description

Impact

When using a custom BuildKit frontend, the frontend can craft an API message that causes files to be written outside of the BuildKit state directory for the execution context.

Patches

The issue has been fixed in v0.28.1+

Workarounds

Issue requires using an untrusted BuildKit frontend set with #syntax or --build-arg BUILDKIT_SYNTAX. Using these options with a well-known frontend image like docker/dockerfile is not affected.

high 8.2: CVE--2026--33748 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range<0.28.1
Fixed version0.28.1
CVSS Score8.2
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS Score0.022%
EPSS Percentile6th percentile
Description

Impact

Insufficient validation of Git URL fragment subdir components (<url>#<ref>:<subdir>, docs) may allow access to files outside the checked-out Git repository root. Possible access is limited to files on the same mounted filesystem.

Patches

The issue has been fixed in version v0.28.1

Workarounds

The issue affects only builds that use Git URLs with a subpath component. Avoid building Dockerfiles from untrusted sources or using the subdir component from an untrusted Git repository where the subdir component could point to a symlink.

critical: 0 high: 0 medium: 2 low: 1 github.com/go-git/go-git/v5 5.13.1 (golang)

pkg:golang/github.com/go-git/go-git@5.13.1#v5

medium 5.0: CVE--2026--34165 Integer Underflow (Wrap or Wraparound)

Affected range>=5.0.0
<=5.17.0
Fixed version5.17.1
CVSS Score5
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:H
EPSS Score0.013%
EPSS Percentile2nd percentile
Description

Impact

A vulnerability has been identified in which a maliciously crafted .idx file can cause asymmetric memory consumption, potentially exhausting available memory and resulting in a Denial of Service (DoS) condition.

Exploitation requires write access to the local repository's .git directory, it order to create or alter existing .idx files.

Patches

Users should upgrade to v5.17.1, or the latest v6 pseudo-version, in order to mitigate this vulnerability.

Credit

The go-git maintainers thank @kq5y for finding and reporting this issue privately to the go-git project.

medium 4.3: CVE--2026--25934 Improper Validation of Integrity Check Value

Affected range<=5.16.4
Fixed version5.16.5
CVSS Score4.3
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
EPSS Score0.006%
EPSS Percentile0th percentile
Description

Impact

A vulnerability was discovered in go-git whereby data integrity values for .pack and .idx files were not properly verified. This resulted in go-git potentially consuming corrupted files, which would likely result in unexpected errors such as object not found.

For context, clients fetch packfiles from upstream Git servers. Those files contain a checksum of their contents, so that clients can perform integrity checks before consuming it. The pack indexes (.idx) are generated locally by go-git, or the git cli, when new .pack files are received and processed. The integrity checks for both files were not being verified correctly.

Note that the lack of verification of the packfile checksum has no impact on the trust relationship between the client and server, which is enforced based on the protocol being used (e.g. TLS in the case of https:// or known hosts for ssh://). In other words, the packfile checksum verification does not provide any security benefits when connecting to a malicious or compromised Git server.

Patches

Users should upgrade to v5.16.5, or the latest v6 pseudo-version, in order to mitigate this vulnerability.

Workarounds

In case updating to a fixed version of go-git is not possible, users can run git fsck from the git cli to check for data corruption on a given repository.

Credit

Thanks @N0zoM1z0 for finding and reporting this issue privately to the go-git project.

low 2.8: CVE--2026--33762 Improper Validation of Array Index

Affected range<=5.17.0
Fixed version5.17.1
CVSS Score2.8
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
EPSS Score0.014%
EPSS Percentile2nd percentile
Description

Impact

go-git’s index decoder for format version 4 fails to validate the path name prefix length before applying it to the previously decoded path name. A maliciously crafted index file can trigger an out-of-bounds slice operation, resulting in a runtime panic during normal index parsing.

This issue only affects Git index format version 4. Earlier formats (go-git supports only v2 and v3) are not vulnerable to this issue.

An attacker able to supply a crafted .git/index file can cause applications using go-git to panic while reading the index. If the application does not recover from panics, this results in process termination, leading to a denial-of-service (DoS) condition.

Exploitation requires the ability to modify or inject a Git index file within the local repository in disk. This typically implies write access to the .git directory.

Patches

Users should upgrade to v5.17.1, or the latest v6 pseudo-version, in order to mitigate this vulnerability.

Credit

go-git maintainers thank @kq5y for finding and reporting this issue privately to the go-git project.

critical: 0 high: 0 medium: 1 low: 0 go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp 1.42.0 (golang)

pkg:golang/go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp@1.42.0

medium 5.3: CVE--2026--39882 Memory Allocation with Excessive Size Value

Affected range<1.43.0
Fixed version1.43.0
CVSS Score5.3
CVSS VectorCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.020%
EPSS Percentile5th percentile
Description

overview:
this report shows that the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap.

this is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection).

severity

HIGH

not claiming: this is a remote dos against every default deployment.
claiming: if the exporter sends traces to an untrusted collector endpoint (or over a network segment where mitm is realistic), that endpoint can crash the process via a large response body.

callsite (pinned):

  • exporters/otlp/otlptrace/otlptracehttp/client.go:199
  • exporters/otlp/otlptrace/otlptracehttp/client.go:230
  • exporters/otlp/otlpmetric/otlpmetrichttp/client.go:170
  • exporters/otlp/otlpmetric/otlpmetrichttp/client.go:201
  • exporters/otlp/otlplog/otlploghttp/client.go:190
  • exporters/otlp/otlplog/otlploghttp/client.go:221

permalinks (pinned):

root cause:
each exporter client reads resp.Body using io.Copy(&respData, resp.Body) into a bytes.Buffer on both success and error paths, with no upper bound.

impact:
a malicious collector can force large transient heap allocations during export (peak memory scales with attacker-chosen response size) and can potentially crash the instrumented process (oom).

affected component:

  • go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp
  • go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp
  • go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp

repro (local-only):

unzip poc.zip -d poc
cd poc
make canonical resp_bytes=33554432 chunk_delay_ms=0

expected output contains:

[CALLSITE_HIT]: otlptracehttp.UploadTraces::io.Copy(resp.Body)
[PROOF_MARKER]: resp_bytes=33554432 peak_alloc_bytes=118050512

control (same env, patched target):

unzip poc.zip -d poc
cd poc
make control resp_bytes=33554432 chunk_delay_ms=0

expected control output contains:

[CALLSITE_HIT]: otlptracehttp.UploadTraces::io.Copy(resp.Body)
[NC_MARKER]: resp_bytes=33554432 peak_alloc_bytes=512232

attachments: poc.zip (attached)

PR_DESCRIPTION.md

attack_scenario.md

poc.zip

Fixed in: open-telemetry/opentelemetry-go#8108

critical: 0 high: 0 medium: 1 low: 0 go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp 1.42.0 (golang)

pkg:golang/go.opentelemetry.io/otel/exporters@1.42.0#otlp/otlpmetric/otlpmetrichttp

medium 5.3: CVE--2026--39882 Memory Allocation with Excessive Size Value

Affected range<1.43.0
Fixed version1.43.0
CVSS Score5.3
CVSS VectorCVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.020%
EPSS Percentile5th percentile
Description

overview:
this report shows that the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap.

this is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection).

severity

HIGH

not claiming: this is a remote dos against every default deployment.
claiming: if the exporter sends traces to an untrusted collector endpoint (or over a network segment where mitm is realistic), that endpoint can crash the process via a large response body.

callsite (pinned):

  • exporters/otlp/otlptrace/otlptracehttp/client.go:199
  • exporters/otlp/otlptrace/otlptracehttp/client.go:230
  • exporters/otlp/otlpmetric/otlpmetrichttp/client.go:170
  • exporters/otlp/otlpmetric/otlpmetrichttp/client.go:201
  • exporters/otlp/otlplog/otlploghttp/client.go:190
  • exporters/otlp/otlplog/otlploghttp/client.go:221

permalinks (pinned):

root cause:
each exporter client reads resp.Body using io.Copy(&respData, resp.Body) into a bytes.Buffer on both success and error paths, with no upper bound.

impact:
a malicious collector can force large transient heap allocations during export (peak memory scales with attacker-chosen response size) and can potentially crash the instrumented process (oom).

affected component:

  • go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp
  • go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp
  • go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp

repro (local-only):

unzip poc.zip -d poc
cd poc
make canonical resp_bytes=33554432 chunk_delay_ms=0

expected output contains:

[CALLSITE_HIT]: otlptracehttp.UploadTraces::io.Copy(resp.Body)
[PROOF_MARKER]: resp_bytes=33554432 peak_alloc_bytes=118050512

control (same env, patched target):

unzip poc.zip -d poc
cd poc
make control resp_bytes=33554432 chunk_delay_ms=0

expected control output contains:

[CALLSITE_HIT]: otlptracehttp.UploadTraces::io.Copy(resp.Body)
[NC_MARKER]: resp_bytes=33554432 peak_alloc_bytes=512232

attachments: poc.zip (attached)

PR_DESCRIPTION.md

attack_scenario.md

poc.zip

Fixed in: open-telemetry/opentelemetry-go#8108

critical: 0 high: 0 medium: 0 low: 1 filippo.io/edwards25519 1.1.0 (golang)

pkg:golang/filippo.io/edwards25519@1.1.0

low 1.7: CVE--2026--26958 Improper Initialization

Affected range<1.1.1
Fixed version1.1.1
CVSS Score1.7
CVSS VectorCVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U
EPSS Score0.018%
EPSS Percentile4th percentile
Description

(*Point).MultiScalarMult failed to initialize its receiver.

If the method was called on an initialized point that is not the identity point, MultiScalarMult produced an incorrect result.

If the method was called on an uninitialized point, the behavior was undefined. In particular, if the receiver was the zero value, MultiScalarMult returned an invalid point that compared Equal to every point.

Note that MultiScalarMult is a rarely used advanced API. For example, if you only depend on filippo.io/edwards25519 via github.com/go-sql-driver/mysql, you are not affected. If you were notified of this issue despite not being affected, consider switching to a vulnerability scanner that is more precise and respectful of your attention, like govulncheck.

critical: 0 high: 0 medium: 0 low: 1 github.com/cloudflare/circl 1.6.1 (golang)

pkg:golang/github.com/cloudflare/circl@1.6.1

low 2.9: CVE--2026--1229 Incorrect Calculation

Affected range<1.6.3
Fixed version1.6.3
CVSS Score2.9
CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:P/S:N/AU:Y/U:Amber
EPSS Score0.022%
EPSS Percentile6th percentile
Description

The CombinedMult function in the CIRCL ecc/p384 package (secp384r1 curve) produces an incorrect value for specific inputs. The issue is fixed by using complete addition formulas.
ECDH and ECDSA signing relying on this curve are not affected.

The bug was fixed in v1.6.3.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 17, 2026

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/24569167653.

@github-actions
Copy link
Copy Markdown

github-actions Bot commented Apr 17, 2026

PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/24569167653.

@github-actions github-actions Bot merged commit c10cc52 into main Apr 17, 2026
9 of 10 checks passed
@github-actions github-actions Bot deleted the renovate/docker-sbx-0.x branch April 17, 2026 14:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@nicholasdille-bot nicholasdille-bot nicholasdille-bot approved these changes

Assignees

No one assigned

Labels

bump/minor type/renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@uniget-bot @nicholasdille-bot @renovate-bot