chore(deps): document CVE-2026-34040 docker/docker AuthZ bypass — patched version unavailable

[Copilot]

Dependabot alert for CVE-2026-34040 / GHSA-x744-4wpc-v9h2 (Moby AuthZ plugin bypass via oversized request bodies) against github.com/docker/docker v28.5.2+incompatible. The fix requires v29.3.1+incompatible, which does not yet exist in the Go module proxy.

Status: Cannot be resolved automatically

• go get github.com/docker/docker@latest resolves to v28.5.2+incompatible — no v29.x is indexed
• testcontainers-go also pins github.com/docker/docker@v28.5.2+incompatible, so both would need simultaneous updates

Reachability Assessment — Not reachable (high confidence)

Advisory is explicit: "If you don't use AuthZ plugins, you are not affected."

• No AuthZ plugin code exists anywhere in the codebase
• github.com/docker/docker is imported only in test files for api/types/container and api/types/mount type definitions (testcontainers integration tests)
• Zero production code touches github.com/docker/docker directly

Affected test files (type imports only):

• pkg/rerankings/hf/huggingface_test.go
• pkg/api/v2/collection_http_integration_test.go
• pkg/api/v2/client_local_crosslang_integration_test.go
• pkg/api/v2/client_http_integration_test.go

Action required (human reviewer)

Monitor the Go module proxy for github.com/docker/docker v29.3.1+incompatible and update both github.com/docker/docker and github.com/testcontainers/testcontainers-go simultaneously when available.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/moby/moby/releases/latest
  • Triggering command: /usr/bin/curl curl -s REDACTED (http block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

Original prompt

---

This section details the Dependabot vulnerability alert you should resolve

<alert_title>Moby has AuthZ plugin bypass when provided oversized request bodies</alert_title>
<alert_description>## Summary

A security vulnerability has been detected that allows attackers to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low.

This is an incomplete fix for CVE-2024-41110.

Impact

If you don't use AuthZ plugins, you are not affected.

Using a specially-crafted API request, an attacker could make the Docker daemon forward the request to an authorization plugin without the body. The authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.

Anyone who depends on authorization plugins that introspect the request body to make access control decisions is potentially impacted.

Workarounds

If unable to update immediately:

• Avoid using AuthZ plugins that rely on request body inspection for security decisions.
• Restrict access to the Docker API to trusted parties, following the principle of least privilege.

Credits

• 1seal / Oleh Konko (@1seal)
• Cody (c@wormhole.guru)
• Asim Viladi Oglu Manizada (@manizada)

Resources

• CVE-2024-41110 / GHSA-v23v-6jw2-98fq</alert_description>

high
GHSA-x744-4wpc-v9h2, CVE-2026-34040
github.com/docker/docker
go
<vulnerable_versions>= v28.5.2+incompatible</vulnerable_versions>
<patched_version></patched_version>
<manifest_path>go.mod</manifest_path>

https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq https://github.com/moby/moby/security/advisories/GHSA-x744-4wpc-v9h2 https://github.com/moby/moby/commit/e89edb19ad7de0407a5d31e3111cb01aa10b5a38 https://docs.docker.com/engine/extend/plugins_authorization https://nvd.nist.gov/vuln/detail/CVE-2026-34040 https://github.com/moby/moby/releases/tag/docker-v29.3.1 https://github.com/advisories/GHSA-x744-4wpc-v9h2

<task_instructions>Resolve this alert by updating the affected package to a non-vulnerable version. Prefer the lowest non-vulnerable version (see the patched_version field above) over the latest to minimize breaking changes. Include a Reachability Assessment section in the PR description. Review the alert_description field to understand which APIs, features, or configurations are affected, then search the codebase for usage of those specific items. If the vulnerable code path is reachable, explain how (which files, APIs, or call sites use the affected functionality) and note that the codebase is actively exposed to this vulnerability. If the vulnerable code path is not reachable, explain why (e.g. the affected API is never called, the vulnerable configuration is not used) and note that the update is primarily to satisfy vulnerability scanners rather than to address an active risk. If the advisory is too vague to determine reachability (e.g. 'improper input validation' with no specific API named), state that reachability could not be determined and explain why. Include a confidence level in the reachability assessment (e.g. high confidence if the advisory names a specific API and you confirmed it is or is not called, low confidence if the usage is indirect and hard to trace). If no patched version is available, check the alert_description field for a Workarounds section — the advisory may describe configuration changes or usage patterns that mitigate the vulnerability without a version update. If a workaround is available, apply it and leave a code comment referencing the advisory identifier explaining it is a temporary mitigation. If neither a patch nor a workaround is available, explain in the PR description why the alert cannot be resolved automatically so a human reviewer can take over. Inspect the repository to determine which package manager is used (e.g. lock files, config files, build scripts) and use that tooling to perform the update — do not edit lock files directly. If the version constraint in the manifest (e.g. package.json, Gemfile, pyproject.toml) caps the version below the fix, update the constraint first. For transitive dependencies, determine whether it is simpler to update the direct dependency that pulls in the vulnerable package or to update the transitive dependency directly, and choose the least disruptive approach. If upgrading to fix the vulnerability forces a major version bump or known breaking changes, review the changelog or release notes, then audit the codebase for usage of affected APIs and fix any breaking ch...

• Resolves amikos-tech/chroma-go alert fix: Fixed the chroma version (0.4.21 was not yet supported by the chart #25