fix(deps): update module github.com/docker/docker to v25.0.13+incompatible [security] (master)

[phisco-renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/docker/docker	v25.0.5+incompatible → v25.0.13+incompatible

---

Warning

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

---

Authz zero length regression

CVE-2024-41110 / GHSA-v23v-6jw2-98fq

More information

Details

A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low. This advisory outlines the issue, identifies the affected versions, and provides remediation steps for impacted users.

Impact

Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.

A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted.

Docker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable.

Vulnerability details

• AuthZ bypass and privilege escalation: An attacker could exploit a bypass using an API request with Content-Length set to 0, causing the Docker daemon to forward the request without the body to the AuthZ plugin, which might approve the request incorrectly.
• Initial fix: The issue was fixed in Docker Engine v18.09.1 January 2019..
• Regression: The fix was not included in Docker Engine v19.03 or newer versions. This was identified in April 2024 and patches were released for the affected versions on July 23, 2024. The issue was assigned CVE-2024-41110.

Patches

• docker-ce v27.1.1 containes patches to fix the vulnerability.
• Patches have also been merged into the master, 19.0, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches.

Remediation steps

• If you are running an affected version, update to the most recent patched version.
• Mitigation if unable to update immediately:
  • Avoid using AuthZ plugins.
  • Restrict access to the Docker API to trusted parties, following the principle of least privilege.

References

• moby/moby@fc274cd
• moby/moby@a79fabb
• https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin/

Severity

• CVSS Score: 9.4 / 10 (Critical)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

References

• https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq
• https://nvd.nist.gov/vuln/detail/CVE-2024-41110
• https://github.com/moby/moby/commit/411e817ddf710ff8e08fa193da80cb78af708191
• https://github.com/moby/moby/commit/42f40b1d6dd7562342f832b9cd2adf9e668eeb76
• https://github.com/moby/moby/commit/65cc597cea28cdc25bea3b8a86384b4251872919
• https://github.com/moby/moby/commit/852759a7df454cbf88db4e954c919becd48faa9b
• https://github.com/moby/moby/commit/a31260625655cff9ae226b51757915e275e304b0
• https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1
• https://github.com/moby/moby/commit/ae160b4edddb72ef4bd71f66b975a1a1cc434f00
• https://github.com/moby/moby/commit/ae2b3666c517c96cbc2adf1af5591a6b00d4ec0f
• https://github.com/moby/moby/commit/cc13f952511154a2866bddbb7dddebfe9e83b801
• https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb
• https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin
• https://github.com/advisories/GHSA-v23v-6jw2-98fq

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Moby firewalld reload removes bridge network isolation

CVE-2025-54410 / GHSA-4vq8-7jfc-9cvp

More information

Details

Moby is an open source container framework developed by Docker Inc. that is distributed as Docker Engine, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (dockerd), which is developed as moby/moby is commonly referred to as Docker, or Docker Engine.

Firewalld is a daemon used by some Linux distributions to provide a dynamically managed firewall. When Firewalld is running, Docker uses its iptables backend to create rules, including rules to isolate containers in one bridge network from containers in other bridge networks.

Impact

The iptables rules created by Docker are removed when firewalld is reloaded using, for example "firewall-cmd --reload", "killall -HUP firewalld", or "systemctl reload firewalld".

When that happens, Docker must re-create the rules. However, in affected versions of Docker, the iptables rules that isolate containers in different bridge networks from each other are not re-created.

Once these rules have been removed, containers have access to any port, on any container, in any non-internal bridge network, running on the Docker host.

Containers running in networks created with --internal or equivalent have no access to other networks. Containers that are only connected to these networks remain isolated after a firewalld reload.

Where Docker Engine is not running in the host's network namespace, it is unaffected. Including, for example, Rootless Mode, and Docker Desktop.

Patches

Moby releases 28.0.0 and newer are not affected. A fix is available in moby release 25.0.13.

Workarounds

After reloading firewalld, either:

• Restart the docker daemon,
• Re-create bridge networks, or
• Use rootless mode.

References

https://firewalld.org/
https://firewalld.org/documentation/howto/reload-firewalld.html

Severity

• CVSS Score: 3.3 / 10 (Low)
• Vector String: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

References

• https://github.com/moby/moby/security/advisories/GHSA-4vq8-7jfc-9cvp
• https://nvd.nist.gov/vuln/detail/CVE-2025-54410
• https://firewalld.org/documentation/howto/reload-firewalld.html
• https://github.com/moby/moby/pull/49443
• https://github.com/moby/moby/pull/49728
• https://github.com/advisories/GHSA-4vq8-7jfc-9cvp

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Authz zero length regression

CVE-2024-41110 / GHSA-v23v-6jw2-98fq / GO-2024-3005

More information

Details

A security vulnerability has been detected in certain versions of Docker Engine, which could allow an attacker to bypass authorization plugins (AuthZ) under specific circumstances. The base likelihood of this being exploited is low. This advisory outlines the issue, identifies the affected versions, and provides remediation steps for impacted users.

Impact

Using a specially-crafted API request, an Engine API client could make the daemon forward the request or response to an authorization plugin without the body. In certain circumstances, the authorization plugin may allow a request which it would have otherwise denied if the body had been forwarded to it.

A security issue was discovered In 2018, where an attacker could bypass AuthZ plugins using a specially crafted API request. This could lead to unauthorized actions, including privilege escalation. Although this issue was fixed in Docker Engine v18.09.1 in January 2019, the fix was not carried forward to later major versions, resulting in a regression. Anyone who depends on authorization plugins that introspect the request and/or response body to make access control decisions is potentially impacted.

Docker EE v19.03.x and all versions of Mirantis Container Runtime are not vulnerable.

Vulnerability details

• AuthZ bypass and privilege escalation: An attacker could exploit a bypass using an API request with Content-Length set to 0, causing the Docker daemon to forward the request without the body to the AuthZ plugin, which might approve the request incorrectly.
• Initial fix: The issue was fixed in Docker Engine v18.09.1 January 2019..
• Regression: The fix was not included in Docker Engine v19.03 or newer versions. This was identified in April 2024 and patches were released for the affected versions on July 23, 2024. The issue was assigned CVE-2024-41110.

Patches

• docker-ce v27.1.1 containes patches to fix the vulnerability.
• Patches have also been merged into the master, 19.0, 20.0, 23.0, 24.0, 25.0, 26.0, and 26.1 release branches.

Remediation steps

• If you are running an affected version, update to the most recent patched version.
• Mitigation if unable to update immediately:
  • Avoid using AuthZ plugins.
  • Restrict access to the Docker API to trusted parties, following the principle of least privilege.

References

• moby/moby@fc274cd
• moby/moby@a79fabb
• https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin/

Severity

• CVSS Score: 9.4 / 10 (Critical)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

References

• https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq
• https://nvd.nist.gov/vuln/detail/CVE-2024-41110
• https://github.com/moby/moby/commit/411e817ddf710ff8e08fa193da80cb78af708191
• https://github.com/moby/moby/commit/42f40b1d6dd7562342f832b9cd2adf9e668eeb76
• https://github.com/moby/moby/commit/65cc597cea28cdc25bea3b8a86384b4251872919
• https://github.com/moby/moby/commit/852759a7df454cbf88db4e954c919becd48faa9b
• https://github.com/moby/moby/commit/a31260625655cff9ae226b51757915e275e304b0
• https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1
• https://github.com/moby/moby/commit/ae160b4edddb72ef4bd71f66b975a1a1cc434f00
• https://github.com/moby/moby/commit/ae2b3666c517c96cbc2adf1af5591a6b00d4ec0f
• https://github.com/moby/moby/commit/cc13f952511154a2866bddbb7dddebfe9e83b801
• https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb
• https://github.com/moby/moby
• https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Moby authz zero length regression in github.com/moby/moby

CVE-2024-41110 / GHSA-v23v-6jw2-98fq / GO-2024-3005

More information

Details

Moby authz zero length regression in github.com/moby/moby

Severity

Unknown

References

• https://nvd.nist.gov/vuln/detail/CVE-2024-41110
• https://github.com/moby/moby/commit/411e817ddf710ff8e08fa193da80cb78af708191
• https://github.com/moby/moby/commit/42f40b1d6dd7562342f832b9cd2adf9e668eeb76
• https://github.com/moby/moby/commit/65cc597cea28cdc25bea3b8a86384b4251872919
• https://github.com/moby/moby/commit/852759a7df454cbf88db4e954c919becd48faa9b
• https://github.com/moby/moby/commit/a31260625655cff9ae226b51757915e275e304b0
• https://github.com/moby/moby/commit/a79fabbfe84117696a19671f4aa88b82d0f64fc1
• https://github.com/moby/moby/commit/ae160b4edddb72ef4bd71f66b975a1a1cc434f00
• https://github.com/moby/moby/commit/ae2b3666c517c96cbc2adf1af5591a6b00d4ec0f
• https://github.com/moby/moby/commit/cc13f952511154a2866bddbb7dddebfe9e83b801
• https://github.com/moby/moby/commit/fc274cd2ff4cf3b48c91697fb327dd1fb95588fb
• https://github.com/moby/moby/security/advisories/GHSA-v23v-6jw2-98fq
• https://www.docker.com/blog/docker-security-advisory-docker-engine-authz-plugin

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).

---

Moby firewalld reload removes bridge network isolation

CVE-2025-54410 / GHSA-4vq8-7jfc-9cvp / GO-2025-3829

More information

Details

Moby is an open source container framework developed by Docker Inc. that is distributed as Docker Engine, Mirantis Container Runtime, and various other downstream projects/products. The Moby daemon component (dockerd), which is developed as moby/moby is commonly referred to as Docker, or Docker Engine.

Firewalld is a daemon used by some Linux distributions to provide a dynamically managed firewall. When Firewalld is running, Docker uses its iptables backend to create rules, including rules to isolate containers in one bridge network from containers in other bridge networks.

Impact

The iptables rules created by Docker are removed when firewalld is reloaded using, for example "firewall-cmd --reload", "killall -HUP firewalld", or "systemctl reload firewalld".

When that happens, Docker must re-create the rules. However, in affected versions of Docker, the iptables rules that isolate containers in different bridge networks from each other are not re-created.

Once these rules have been removed, containers have access to any port, on any container, in any non-internal bridge network, running on the Docker host.

Containers running in networks created with --internal or equivalent have no access to other networks. Containers that are only connected to these networks remain isolated after a firewalld reload.

Where Docker Engine is not running in the host's network namespace, it is unaffected. Including, for example, Rootless Mode, and Docker Desktop.

Patches

Moby releases 28.0.0 and newer are not affected. A fix is available in moby release 25.0.13.

Workarounds

After reloading firewalld, either:

• Restart the docker daemon,
• Re-create bridge networks, or
• Use rootless mode.

References

https://firewalld.org/
https://firewalld.org/documentation/howto/reload-firewalld.html

Severity

• CVSS Score: 3.3 / 10 (Low)
• Vector String: CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

References

• https://github.com/moby/moby/security/advisories/GHSA-4vq8-7jfc-9cvp
• https://nvd.nist.gov/vuln/detail/CVE-2025-54410
• https://github.com/moby/moby/pull/49443
• https://github.com/moby/moby/pull/49728
• https://firewalld.org/documentation/howto/reload-firewalld.html
• https://github.com/moby/moby

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Moby firewalld reload removes bridge network isolation in github.com/docker/docker

CVE-2025-54410 / GHSA-4vq8-7jfc-9cvp / GO-2025-3829

More information

Details

Moby firewalld reload removes bridge network isolation in github.com/docker/docker

Severity

Unknown

References

• https://github.com/moby/moby/security/advisories/GHSA-4vq8-7jfc-9cvp
• https://firewalld.org/documentation/howto/reload-firewalld.html

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).

---

Release Notes

docker/docker (github.com/docker/docker)

v25.0.13+incompatible

Compare Source

v25.0.12+incompatible

Compare Source

v25.0.11+incompatible

Compare Source

v25.0.10+incompatible

Compare Source

v25.0.9+incompatible

Compare Source

v25.0.8+incompatible

Compare Source

v25.0.7+incompatible

Compare Source

v25.0.6+incompatible

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • ""
• 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 Mend Renovate.