Skip to content

deps(deps): update ansible/ansible-lint action to v25.12.0 #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
renovate wants to merge 1 commit into
base: master
Choose a base branch
from
Open

deps(deps): update ansible/ansible-lint action to v25.12.0 #96

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 29, 2025 •
edited
Loading

This PR contains the following updates:

Package Type Update Change
ansible/ansible-lint action minor v25.6.1 -> v25.12.0

Release Notes

ansible/ansible-lint (ansible/ansible-lint)

v25.12.0

Compare Source

Maintenance

v25.11.1

Compare Source

Features

Fixes

Maintenance

v25.11.0

Compare Source

Fixes

Maintenance

v25.9.2

Compare Source

Fixes

Maintenance

v25.9.1

Compare Source

Fixes

Maintenance

v25.9.0

Compare Source

Fixes

Maintenance

v25.8.2

Compare Source

Bugfixes

v25.8.1

Compare Source

Bugfixes

  • Fix first-run collection discovery by enabling plugin loader after prepare_environment (#​4722) @​cidrblock

Maintenance

v25.8.0

Compare Source

Bugfixes

v25.7.0

Compare Source

Enhancements

Bugfixes

Maintenance

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from lotyp as a code owner July 29, 2025 20:28
@renovate renovate bot enabled auto-merge (squash) July 29, 2025 20:28
@github-actions github-actions bot added the type: maintenance For maintenance, refactor and testing (perf, chore, style, revert, refactor, test, build, ci) label Jul 29, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Jul 29, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:f7c9ecf8281e65b0775cd6cc4753b41b0dbeed254f10aafe9a63efb79a9423d4
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.0-alpine
  • 1.29.0-alpine3.22
  • alpine
  • alpine3.22
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:845b5424415de5f77dd5753cbb7c1be8bd8e44cc81f20f9705783a02f8848317
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0

@github-actions
Copy link
Contributor

github-actions bot commented Jul 29, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.0-alpine
Digestsha256:845b5424415de5f77dd5753cbb7c1be8bd8e44cc81f20f9705783a02f8848317
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed1 month ago
Size22 MB
Packages86
Flavoralpine
Runtime1.29.0
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.0-alpine, 1.29.0-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.0-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • 1.29-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29.0-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.0
 1 month ago



@github-actions
Copy link
Contributor

github-actions bot commented Jul 29, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:9434016e98c62a1d6576d07ad212a53746502cab47881033b5734ecd9e80311e
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.0-alpine
  • 1.29.0-alpine3.22
  • alpine
  • alpine3.22
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:845b5424415de5f77dd5753cbb7c1be8bd8e44cc81f20f9705783a02f8848317
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0

@github-actions
Copy link
Contributor

github-actions bot commented Jul 29, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.0-alpine
Digestsha256:845b5424415de5f77dd5753cbb7c1be8bd8e44cc81f20f9705783a02f8848317
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed1 month ago
Size22 MB
Packages86
Flavoralpine
Runtime1.29.0
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.0-alpine, 1.29.0-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.0-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • 1.29-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29.0-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.0
 1 month ago



@renovate renovate bot changed the title deps(deps): update ansible/ansible-lint action to v25.7.0 deps(deps): update ansible/ansible-lint action to v25.8.0 Aug 13, 2025
@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from cca6828 to dc514ba Compare August 13, 2025 17:33
@github-actions
Copy link
Contributor

github-actions bot commented Aug 13, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:25560c561c518b066639eda9710106ad083aa3bac8af309444266e5112b8a336
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.0-alpine
  • 1.29.0-alpine3.22
  • alpine
  • alpine3.22
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:845b5424415de5f77dd5753cbb7c1be8bd8e44cc81f20f9705783a02f8848317
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0

@github-actions
Copy link
Contributor

github-actions bot commented Aug 13, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.0-alpine
Digestsha256:845b5424415de5f77dd5753cbb7c1be8bd8e44cc81f20f9705783a02f8848317
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed1 month ago
Size22 MB
Packages86
Flavoralpine
Runtime1.29.0
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.0-alpine, 1.29.0-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.0-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • 1.29-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29.0-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.0
 1 month ago



@github-actions
Copy link
Contributor

github-actions bot commented Aug 13, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:1aa1ea954de94d4338cf3402f1823dde79f61edfc4216a6d92c925ffd5efd7dd
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.0-alpine
  • 1.29.0-alpine3.22
  • alpine
  • alpine3.22
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:845b5424415de5f77dd5753cbb7c1be8bd8e44cc81f20f9705783a02f8848317
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0

@github-actions
Copy link
Contributor

github-actions bot commented Aug 13, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.0-alpine
Digestsha256:845b5424415de5f77dd5753cbb7c1be8bd8e44cc81f20f9705783a02f8848317
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed1 month ago
Size22 MB
Packages86
Flavoralpine
Runtime1.29.0
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.0-alpine, 1.29.0-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.0-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • 1.29-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29.0-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.0
 1 month ago



@renovate renovate bot changed the title deps(deps): update ansible/ansible-lint action to v25.8.0 deps(deps): update ansible/ansible-lint action to v25.8.1 Aug 14, 2025
@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from dc514ba to cbb1b9d Compare August 14, 2025 03:54
@github-actions
Copy link
Contributor

github-actions bot commented Aug 14, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:cf042518c787308b4f66778ae7435d311fb6323393e8e283f27b0382c890a4c0
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.1-alpine
  • 1.29.1-alpine3.22
  • alpine
  • alpine3.22
  • d6f888f021e56e2d8de9494593eb83a28241fbb50d24b52528c7098edeb05767
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:60e48a050b6408d0c5dd59b98b6e36bf0937a0bbe99304e3e9c0e63b7563443a
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0

@github-actions
Copy link
Contributor

github-actions bot commented Aug 14, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.1-alpine
Digestsha256:60e48a050b6408d0c5dd59b98b6e36bf0937a0bbe99304e3e9c0e63b7563443a
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed11 hours ago
Size22 MB
Packages86
Flavoralpine
Runtime1.29.1
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.1-alpine, 1.29.1-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.1-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29-alpine3.22-slim
  • 1.29.1-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.1
 11 hours ago



@github-actions
Copy link
Contributor

github-actions bot commented Aug 14, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:25df08b9608159e4663ba3016130e4409d12a5b6f5fa1ae748b93aaa62608d07
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.1-alpine
  • 1.29.1-alpine3.22
  • alpine
  • alpine3.22
  • d6f888f021e56e2d8de9494593eb83a28241fbb50d24b52528c7098edeb05767
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:60e48a050b6408d0c5dd59b98b6e36bf0937a0bbe99304e3e9c0e63b7563443a
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0

@github-actions
Copy link
Contributor

github-actions bot commented Aug 14, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.1-alpine
Digestsha256:60e48a050b6408d0c5dd59b98b6e36bf0937a0bbe99304e3e9c0e63b7563443a
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed11 hours ago
Size22 MB
Packages86
Flavoralpine
Runtime1.29.1
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.1-alpine, 1.29.1-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.1-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29-alpine3.22-slim
  • 1.29.1-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.1
 11 hours ago



@renovate renovate bot changed the title deps(deps): update ansible/ansible-lint action to v25.8.1 deps(deps): update ansible/ansible-lint action to v25.8.2 Aug 21, 2025
@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from cbb1b9d to 9e958d1 Compare August 21, 2025 18:34
@github-actions
Copy link
Contributor

github-actions bot commented Aug 21, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:0349fd75dcb93a8099b12afbe181cb7d8d68a6f2fed5b1f057ed6c19552bf7af
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.1-alpine
  • 1.29.1-alpine3.22
  • alpine
  • alpine3.22
  • d6f888f021e56e2d8de9494593eb83a28241fbb50d24b52528c7098edeb05767
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:60e48a050b6408d0c5dd59b98b6e36bf0937a0bbe99304e3e9c0e63b7563443a
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0

@github-actions
Copy link
Contributor

github-actions bot commented Aug 21, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.1-alpine
Digestsha256:60e48a050b6408d0c5dd59b98b6e36bf0937a0bbe99304e3e9c0e63b7563443a
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed1 week ago
Size22 MB
Packages86
Flavoralpine
Runtime1.29.1
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.1-alpine, 1.29.1-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.1-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • 1.29-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29.1-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.1
 1 week ago



@github-actions
Copy link
Contributor

github-actions bot commented Aug 21, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:98efd5d66fce1d3d26b53ee96e45a6bd11da3502e708299e936327baea9dad53
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.1-alpine
  • 1.29.1-alpine3.22
  • alpine
  • alpine3.22
  • d6f888f021e56e2d8de9494593eb83a28241fbb50d24b52528c7098edeb05767
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:60e48a050b6408d0c5dd59b98b6e36bf0937a0bbe99304e3e9c0e63b7563443a
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0

@github-actions
Copy link
Contributor

github-actions bot commented Aug 21, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.1-alpine
Digestsha256:60e48a050b6408d0c5dd59b98b6e36bf0937a0bbe99304e3e9c0e63b7563443a
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed1 week ago
Size22 MB
Packages86
Flavoralpine
Runtime1.29.1
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.1-alpine, 1.29.1-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.1-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • 1.29-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29.1-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.1
 1 week ago



@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from 9e958d1 to 4300bb6 Compare September 16, 2025 15:05
@renovate renovate bot changed the title deps(deps): update ansible/ansible-lint action to v25.8.2 deps(deps): update ansible/ansible-lint action to v25.9.0 Sep 16, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Sep 16, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of tonistiigi/binfmt:latest

📦 Image Reference tonistiigi/binfmt:latest
digestsha256:c97f15e717f7eb99d237e46f0a3553da8cfdf470a15bba459c056d90d0e398f5
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size35 MB
packages13

1 similar comment
@github-actions
Copy link
Contributor

github-actions bot commented Sep 16, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of tonistiigi/binfmt:latest

📦 Image Reference tonistiigi/binfmt:latest
digestsha256:c97f15e717f7eb99d237e46f0a3553da8cfdf470a15bba459c056d90d0e398f5
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size35 MB
packages13

@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from 4300bb6 to 66c1ae6 Compare October 1, 2025 20:59
@renovate renovate bot changed the title deps(deps): update ansible/ansible-lint action to v25.9.0 deps(deps): update ansible/ansible-lint action to v25.9.1 Oct 1, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 1, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of tonistiigi/binfmt:latest

📦 Image Reference tonistiigi/binfmt:latest
digestsha256:c97f15e717f7eb99d237e46f0a3553da8cfdf470a15bba459c056d90d0e398f5
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size35 MB
packages13

1 similar comment
@github-actions
Copy link
Contributor

github-actions bot commented Oct 1, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of tonistiigi/binfmt:latest

📦 Image Reference tonistiigi/binfmt:latest
digestsha256:c97f15e717f7eb99d237e46f0a3553da8cfdf470a15bba459c056d90d0e398f5
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size35 MB
packages13

@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from 66c1ae6 to ef7b017 Compare October 8, 2025 15:44
@renovate renovate bot changed the title deps(deps): update ansible/ansible-lint action to v25.9.1 deps(deps): update ansible/ansible-lint action to v25.9.2 Oct 8, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 8, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:b56f51142f61f402a9582e023f7781061636854d3cf8dac99f239751717c8e0e
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size31 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.2-alpine
  • 1.29.2-alpine3.22
  • alpine
  • alpine3.22
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:5105ff1d2f8c81a83c335cee9bf466f452e33d7ea58ef0e7065143fb761485ab
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2

@github-actions
Copy link
Contributor

github-actions bot commented Oct 8, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.2-alpine
Digestsha256:5105ff1d2f8c81a83c335cee9bf466f452e33d7ea58ef0e7065143fb761485ab
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
Pushed18 hours ago
Size25 MB
Packages87
Flavoralpine
Runtime1.29.2
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.2-alpine, 1.29.2-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.2-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29-alpine3.22-slim
  • 1.29.2-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 61 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 8.1 MB
  • Flavor: alpine
  • Runtime: 1.29.2
 18 hours ago



@github-actions
Copy link
Contributor

github-actions bot commented Oct 8, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:4ecfa79d798a02366238c63a8febb709e5675e1bdd42c7e9e4936ccc06f132ed
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size31 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.2-alpine
  • 1.29.2-alpine3.22
  • alpine
  • alpine3.22
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:5105ff1d2f8c81a83c335cee9bf466f452e33d7ea58ef0e7065143fb761485ab
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2

@github-actions
Copy link
Contributor

github-actions bot commented Oct 8, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.2-alpine
Digestsha256:5105ff1d2f8c81a83c335cee9bf466f452e33d7ea58ef0e7065143fb761485ab
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
Pushed18 hours ago
Size25 MB
Packages87
Flavoralpine
Runtime1.29.2
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.2-alpine, 1.29.2-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.2-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29-alpine3.22-slim
  • 1.29.2-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 61 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 8.1 MB
  • Flavor: alpine
  • Runtime: 1.29.2
 18 hours ago



@renovate renovate bot changed the title deps(deps): update ansible/ansible-lint action to v25.9.2 deps(deps): update ansible/ansible-lint action to v25.11.0 Nov 10, 2025
@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from ef7b017 to 90a0984 Compare November 10, 2025 23:58
@github-actions
Copy link
Contributor

github-actions bot commented Nov 10, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:f541d1713708bbf480736c22333899c4c2d292ac4e4f12a06b77dd717bf62edd
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.3-alpine
  • 1.29.3-alpine3.22
  • alpine
  • alpine3.22
  • cdd9299699667dcc3b926ba8bb10ddaf851037e002cee9360afe59847243c96e
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:667473807103639a0aca5b49534a216d2b64f0fb868aaa801f023da0cdd781c7
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2

@github-actions
Copy link
Contributor

github-actions bot commented Nov 10, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/nginx:latest

📦 Image Reference wayofdev/nginx:latest
digestsha256:ba00e2c4e65f8b4358e3462096b90e801fd96fcfed46b3c1d179cd4ee53774e3
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
platformlinux/amd64
size28 MB
packages86
📦 Base Image nginx:1-alpine
also known as
  • 1-alpine3.22
  • 1.29-alpine
  • 1.29-alpine3.22
  • 1.29.3-alpine
  • 1.29.3-alpine3.22
  • alpine
  • alpine3.22
  • cdd9299699667dcc3b926ba8bb10ddaf851037e002cee9360afe59847243c96e
  • mainline-alpine
  • mainline-alpine3.22
digestsha256:667473807103639a0aca5b49534a216d2b64f0fb868aaa801f023da0cdd781c7
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2

@github-actions
Copy link
Contributor

github-actions bot commented Nov 10, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.3-alpine
Digestsha256:667473807103639a0aca5b49534a216d2b64f0fb868aaa801f023da0cdd781c7
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
Pushed1 week ago
Size23 MB
Packages86
Flavoralpine
Runtime1.29.3
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.3-alpine, 1.29.3-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.3-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29-alpine3.22-slim
  • 1.29.3-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.3
 1 week ago



1 similar comment
@github-actions
Copy link
Contributor

github-actions bot commented Nov 10, 2025 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/nginx:latest

Base image is nginx:1-alpine

Name1.29.3-alpine
Digestsha256:667473807103639a0aca5b49534a216d2b64f0fb868aaa801f023da0cdd781c7
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
Pushed1 week ago
Size23 MB
Packages86
Flavoralpine
Runtime1.29.3
The base image is also available under the supported tag(s): 1-alpine3.22, 1.29-alpine, 1.29-alpine3.22, 1.29.3-alpine, 1.29.3-alpine3.22, alpine, alpine3.22, mainline-alpine, mainline-alpine3.22

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
1-alpine-slim
Minor runtime version update
Also known as:
  • 1.29.3-alpine-slim
  • 1.29-alpine-slim
  • alpine-slim
  • alpine3.22-slim
  • 1-alpine3.22-slim
  • mainline-alpine-slim
  • 1.29-alpine3.22-slim
  • 1.29.3-alpine3.22-slim
  • mainline-alpine3.22-slim
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image is smaller by 16 MB
  • Image contains 60 fewer packages
  • Image has same number of vulnerabilities
  • Tag is using slim variant
  • 1-alpine-slim was pulled 215K times last month
Image details:
  • Size: 5.6 MB
  • Flavor: alpine
  • Runtime: 1.29.3
 1 week ago



@renovate renovate bot changed the title deps(deps): update ansible/ansible-lint action to v25.11.0 deps(deps): update ansible/ansible-lint action to v25.11.1 Nov 24, 2025
@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from 90a0984 to bf18914 Compare November 24, 2025 21:32
@github-actions
Copy link
Contributor

github-actions bot commented Nov 24, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of moby/buildkit:buildx-stable-1

📦 Image Reference moby/buildkit:buildx-stable-1
digestsha256:fe0990fb85c4586aaa94e599905b75a2676664f065f29bea67ebcd5b2fe88acb
vulnerabilitiescritical: 0 high: 6 medium: 0 low: 0
platformlinux/amd64
size111 MB
packages251
📦 Base Image alpine:3
also known as
  • 3.22
  • 3.22.2
  • af829cb99e2e0ed9843029ba4b20af63bf652e3f57b9aaa049744a8b64d7c608
  • latest
digestsha256:85f2b723e106c34644cd5851d7e81ee87da98ac54672b29947c052a45d31dc2f
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
critical: 0 high: 4 medium: 0 low: 0 stdlib 1.25.0 (golang)

pkg:golang/stdlib@1.25.0

high : CVE--2025--61725

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.024%
EPSS Percentile5th percentile
Description

The ParseAddress function constructeds domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

high : CVE--2025--61723

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.024%
EPSS Percentile5th percentile
Description

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.

This affects programs which parse untrusted PEM inputs.

high : CVE--2025--58188

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.013%
EPSS Percentile1st percentile
Description

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

high : CVE--2025--58187

Affected range>=1.25.0
<1.25.3
Fixed version1.25.3
EPSS Score0.013%
EPSS Percentile1st percentile
Description

Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

critical: 0 high: 1 medium: 0 low: 0 github.com/opencontainers/selinux 1.12.0 (golang)

pkg:golang/github.com/opencontainers/selinux@1.12.0

high 7.3: CVE--2025--52881 Race Condition Enabling Link Following

Affected range<=1.12.0
Fixed version1.13.0
CVSS Score7.3
CVSS VectorCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
EPSS Score0.018%
EPSS Percentile3rd percentile
Description

Impact

This attack is primarily a more sophisticated version of CVE-2019-19921, which was a flaw which allowed an attacker to trick runc into writing the LSM process labels for a container process into a dummy tmpfs file and thus not apply the correct LSM labels to the container process. The mitigation runc applied for CVE-2019-19921 was fairly limited and effectively only caused runc to verify that when runc writes LSM labels that those labels are actual procfs files.

Rather than using a fake tmpfs file for /proc/self/attr/<label>, an attacker could instead (through various means) make /proc/self/attr/<label> reference a real procfs file, but one that would still be a no-op (such as /proc/self/sched). This would have the same effect but would clear the "is a procfs file" check. Runc is aware that this kind of attack would be possible (even going so far as to discuss this publicly as "future work" at conferences), and runc is working on a far more comprehensive mitigation of this attack, but this security issue was disclosed before runc could complete this work.

In all known versions of runc, an attacker can trick runc into misdirecting writes to /proc to other procfs files through the use of a racing container with shared mounts (runc has also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts.

Note that while /proc/self/attr/<label> was the example used above (which is LSM-specific), this issue affect all writes to /proc in runc and thus also affects sysctls (written to /proc/sys/...) and some other APIs.

Additional Impacts

While investigating this issue, runc discovered that another risk with these redirected writes is that they could be redirected to dangerous files such as /proc/sysrq-trigger rather than just no-op files like /proc/self/sched. For instance, the default AppArmor profile name in Docker is docker-default, which when written to /proc/sysrq-trigger would cause the host system to crash.

When this was discovered, runc conducted an audit of other write operations within runc and found several possible areas where runc could be used as a semi-arbitrary write gadget when combined with the above race attacks. The most concerning attack scenario was the configuration of sysctls. Because the contents of the sysctl are free-form text, an attacker could use a misdirected write to write to /proc/sys/kernel/core_pattern and break out of the container (as described in CVE-2025-31133, kernel upcalls are not namespaced and so coredump helpers will run with complete root privileges on the host). Even if the attacker cannot configure custom sysctls, a valid sysctl string (when redirected to /proc/sysrq-trigger) can easily cause the machine to hang.

Note that the fact that this attack allows you to disable LSM labels makes it a very useful attack to combine with CVE-2025-31133 (as one of the only mitigations available to most users for that issue is AppArmor, and this attack would let you bypass that). However, the misdirected write issue above means that you could also achieve most of the same goals without needing to chain together attacks.

Patches

This advisory is being published as part of a set of three advisories:

  • CVE-2025-31133
  • CVE-2025-52881
  • CVE-2025-52565

The patches fixing this issue have accordingly been combined into a single patchset. The following patches from that patchset resolve the issues in this advisory:

  • db19bbed5348 ("internal/sys: add VerifyInode helper")
  • 6fc191449109 ("internal: move utils.MkdirAllInRoot to internal/pathrs")
  • ff94f9991bd3 ("*: switch to safer securejoin.Reopen")
  • 44a0fcf685db ("go.mod: update to github.com/cyphar/filepath-securejoin@v0.5.0")
  • 77889b56db93 ("internal: add wrappers for securejoin.Proc*")
  • fdcc9d3cad2f ("apparmor: use safe procfs API for labels")
  • ff6fe1324663 ("utils: use safe procfs for /proc/self/fd loop code")
  • b3dd1bc562ed ("utils: remove unneeded EnsureProcHandle")
  • 77d217c7c377 ("init: write sysctls using safe procfs API")
  • 435cc81be6b7 ("init: use securejoin for /proc/self/setgroups")
  • d61fd29d854b ("libct/system: use securejoin for /proc/$pid/stat")
  • 4b37cd93f86e ("libct: align param type for mountCgroupV1/V2 functions")
  • d40b3439a961 ("rootfs: switch to fd-based handling of mountpoint targets")
  • ed6b1693b8b3 ("selinux: use safe procfs API for labels")

    • Please note that this patch includes a private patch for github.com/opencontainers/selinux that could not be made public through a public pull request (as it would necessarily disclose this embargoed security issue).

      The patch includes a complete copy of the forked code and a replace directive (as well as go mod vendor applied), which should still work with downstream build systems. If you cannot apply this patch, you can safely drop it -- some of the other patches in this series should block these kinds of racing mount attacks entirely.

      See selinux: migrate to pathrs-lite procfs API opencontainers/selinux#237 for the upstream patch.

  • 3f925525b44d ("rootfs: re-allow dangling symlinks in mount targets")
  • a41366e74080 ("openat2: improve resilience on busy systems")

runc 1.2.8, 1.3.3, and 1.4.0-rc.3 have been released and all contain fixes for these issues. As per runc's new release model, runc 1.1.x and earlier are no longer supported and thus have not been patched.

Mitigations

  • Do not run untrusted container images from unknown or unverified sources.

  • For the basic no-op attack, this attack allows a container process to run with the same LSM labels as runc. For most AppArmor deployments this means it will be unconfined, and for SELinux it will likely be container_runtime_t. Runc has not conducted in-depth testing of the impact on SELinux -- it is possible that it provides some reasonable protection but it seems likely that an attacker could cause harm to systems even with such an SELinux setup.

  • For the more involved redirect and write gadget attacks, unfortunately most LSM profiles (including the standard container-selinux profiles) provide the container runtime access to sysctl files (including /proc/sysrq-trigger) and so LSMs likely do not provide much protection against these attacks.

  • Using rootless containers provides some protection against these kinds of bugs (privileged writes in runc being redirected) -- by having runc itself be an unprivileged process, in general you would expect the impact scope of a runc bug to be less severe as it would only have the privileges afforded to the host user which spawned runc. For this particular bug, the privilege escalation caused by the inadvertent write issue is entirely mitigated with rootless containers because the unprivileged user that the runc process is executing as cannot write to the aforementioned procfs files (even intentionally).

Other Runtimes

As this vulnerability boils down to a fairly easy-to-make logic bug, runc has provided information to other OCI (crun, youki) and non-OCI (LXC) container runtimes about this vulnerability.

Based on discussions with other runtimes, it seems that crun and youki may have similar security issues and will release a co-ordinated security release along with runc. LXC appears to use the host's /proc for all procfs operations, and so is likely not vulnerable to this issue (this is a trade-off -- runc uses the container's procfs to avoid CVE-2016-9962-style attacks).

Credits

Thanks to Li Fubang (@lifubang from acmcoder.com, CIIC) and Tõnis Tiigi (@tonistiigi from Docker) for both independently discovering this vulnerability, as well as Aleksa Sarai (@cyphar from SUSE) for the original research into this class of security issues and solutions.

Additional thanks go to Tõnis Tiigi for finding some very useful exploit templates for these kinds of race attacks using docker buildx build.

critical: 0 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.42.0 (golang)

pkg:golang/golang.org/x/crypto@0.42.0

high : CVE--2025--47913

Affected range<0.43.0
Fixed version0.43.0
EPSS Score0.018%
EPSS Percentile3rd percentile
Description

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 24, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of moby/buildkit:buildx-stable-1

📦 Image Reference moby/buildkit:buildx-stable-1
digestsha256:fe0990fb85c4586aaa94e599905b75a2676664f065f29bea67ebcd5b2fe88acb
vulnerabilitiescritical: 0 high: 6 medium: 0 low: 0
platformlinux/amd64
size111 MB
packages251
📦 Base Image alpine:3
also known as
  • 3.22
  • 3.22.2
  • af829cb99e2e0ed9843029ba4b20af63bf652e3f57b9aaa049744a8b64d7c608
  • latest
digestsha256:85f2b723e106c34644cd5851d7e81ee87da98ac54672b29947c052a45d31dc2f
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
critical: 0 high: 4 medium: 0 low: 0 stdlib 1.25.0 (golang)

pkg:golang/stdlib@1.25.0

high : CVE--2025--61725

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.024%
EPSS Percentile5th percentile
Description

The ParseAddress function constructeds domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

high : CVE--2025--61723

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.024%
EPSS Percentile5th percentile
Description

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.

This affects programs which parse untrusted PEM inputs.

high : CVE--2025--58188

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.013%
EPSS Percentile1st percentile
Description

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

high : CVE--2025--58187

Affected range>=1.25.0
<1.25.3
Fixed version1.25.3
EPSS Score0.013%
EPSS Percentile1st percentile
Description

Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

critical: 0 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.42.0 (golang)

pkg:golang/golang.org/x/crypto@0.42.0

high : CVE--2025--47913

Affected range<0.43.0
Fixed version0.43.0
EPSS Score0.018%
EPSS Percentile3rd percentile
Description

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

critical: 0 high: 1 medium: 0 low: 0 github.com/opencontainers/selinux 1.12.0 (golang)

pkg:golang/github.com/opencontainers/selinux@1.12.0

high 7.3: CVE--2025--52881 Race Condition Enabling Link Following

Affected range<=1.12.0
Fixed version1.13.0
CVSS Score7.3
CVSS VectorCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
EPSS Score0.018%
EPSS Percentile3rd percentile
Description

Impact

This attack is primarily a more sophisticated version of CVE-2019-19921, which was a flaw which allowed an attacker to trick runc into writing the LSM process labels for a container process into a dummy tmpfs file and thus not apply the correct LSM labels to the container process. The mitigation runc applied for CVE-2019-19921 was fairly limited and effectively only caused runc to verify that when runc writes LSM labels that those labels are actual procfs files.

Rather than using a fake tmpfs file for /proc/self/attr/<label>, an attacker could instead (through various means) make /proc/self/attr/<label> reference a real procfs file, but one that would still be a no-op (such as /proc/self/sched). This would have the same effect but would clear the "is a procfs file" check. Runc is aware that this kind of attack would be possible (even going so far as to discuss this publicly as "future work" at conferences), and runc is working on a far more comprehensive mitigation of this attack, but this security issue was disclosed before runc could complete this work.

In all known versions of runc, an attacker can trick runc into misdirecting writes to /proc to other procfs files through the use of a racing container with shared mounts (runc has also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts.

Note that while /proc/self/attr/<label> was the example used above (which is LSM-specific), this issue affect all writes to /proc in runc and thus also affects sysctls (written to /proc/sys/...) and some other APIs.

Additional Impacts

While investigating this issue, runc discovered that another risk with these redirected writes is that they could be redirected to dangerous files such as /proc/sysrq-trigger rather than just no-op files like /proc/self/sched. For instance, the default AppArmor profile name in Docker is docker-default, which when written to /proc/sysrq-trigger would cause the host system to crash.

When this was discovered, runc conducted an audit of other write operations within runc and found several possible areas where runc could be used as a semi-arbitrary write gadget when combined with the above race attacks. The most concerning attack scenario was the configuration of sysctls. Because the contents of the sysctl are free-form text, an attacker could use a misdirected write to write to /proc/sys/kernel/core_pattern and break out of the container (as described in CVE-2025-31133, kernel upcalls are not namespaced and so coredump helpers will run with complete root privileges on the host). Even if the attacker cannot configure custom sysctls, a valid sysctl string (when redirected to /proc/sysrq-trigger) can easily cause the machine to hang.

Note that the fact that this attack allows you to disable LSM labels makes it a very useful attack to combine with CVE-2025-31133 (as one of the only mitigations available to most users for that issue is AppArmor, and this attack would let you bypass that). However, the misdirected write issue above means that you could also achieve most of the same goals without needing to chain together attacks.

Patches

This advisory is being published as part of a set of three advisories:

  • CVE-2025-31133
  • CVE-2025-52881
  • CVE-2025-52565

The patches fixing this issue have accordingly been combined into a single patchset. The following patches from that patchset resolve the issues in this advisory:

  • db19bbed5348 ("internal/sys: add VerifyInode helper")
  • 6fc191449109 ("internal: move utils.MkdirAllInRoot to internal/pathrs")
  • ff94f9991bd3 ("*: switch to safer securejoin.Reopen")
  • 44a0fcf685db ("go.mod: update to github.com/cyphar/filepath-securejoin@v0.5.0")
  • 77889b56db93 ("internal: add wrappers for securejoin.Proc*")
  • fdcc9d3cad2f ("apparmor: use safe procfs API for labels")
  • ff6fe1324663 ("utils: use safe procfs for /proc/self/fd loop code")
  • b3dd1bc562ed ("utils: remove unneeded EnsureProcHandle")
  • 77d217c7c377 ("init: write sysctls using safe procfs API")
  • 435cc81be6b7 ("init: use securejoin for /proc/self/setgroups")
  • d61fd29d854b ("libct/system: use securejoin for /proc/$pid/stat")
  • 4b37cd93f86e ("libct: align param type for mountCgroupV1/V2 functions")
  • d40b3439a961 ("rootfs: switch to fd-based handling of mountpoint targets")
  • ed6b1693b8b3 ("selinux: use safe procfs API for labels")

    • Please note that this patch includes a private patch for github.com/opencontainers/selinux that could not be made public through a public pull request (as it would necessarily disclose this embargoed security issue).

      The patch includes a complete copy of the forked code and a replace directive (as well as go mod vendor applied), which should still work with downstream build systems. If you cannot apply this patch, you can safely drop it -- some of the other patches in this series should block these kinds of racing mount attacks entirely.

      See selinux: migrate to pathrs-lite procfs API opencontainers/selinux#237 for the upstream patch.

  • 3f925525b44d ("rootfs: re-allow dangling symlinks in mount targets")
  • a41366e74080 ("openat2: improve resilience on busy systems")

runc 1.2.8, 1.3.3, and 1.4.0-rc.3 have been released and all contain fixes for these issues. As per runc's new release model, runc 1.1.x and earlier are no longer supported and thus have not been patched.

Mitigations

  • Do not run untrusted container images from unknown or unverified sources.

  • For the basic no-op attack, this attack allows a container process to run with the same LSM labels as runc. For most AppArmor deployments this means it will be unconfined, and for SELinux it will likely be container_runtime_t. Runc has not conducted in-depth testing of the impact on SELinux -- it is possible that it provides some reasonable protection but it seems likely that an attacker could cause harm to systems even with such an SELinux setup.

  • For the more involved redirect and write gadget attacks, unfortunately most LSM profiles (including the standard container-selinux profiles) provide the container runtime access to sysctl files (including /proc/sysrq-trigger) and so LSMs likely do not provide much protection against these attacks.

  • Using rootless containers provides some protection against these kinds of bugs (privileged writes in runc being redirected) -- by having runc itself be an unprivileged process, in general you would expect the impact scope of a runc bug to be less severe as it would only have the privileges afforded to the host user which spawned runc. For this particular bug, the privilege escalation caused by the inadvertent write issue is entirely mitigated with rootless containers because the unprivileged user that the runc process is executing as cannot write to the aforementioned procfs files (even intentionally).

Other Runtimes

As this vulnerability boils down to a fairly easy-to-make logic bug, runc has provided information to other OCI (crun, youki) and non-OCI (LXC) container runtimes about this vulnerability.

Based on discussions with other runtimes, it seems that crun and youki may have similar security issues and will release a co-ordinated security release along with runc. LXC appears to use the host's /proc for all procfs operations, and so is likely not vulnerable to this issue (this is a trade-off -- runc uses the container's procfs to avoid CVE-2016-9962-style attacks).

Credits

Thanks to Li Fubang (@lifubang from acmcoder.com, CIIC) and Tõnis Tiigi (@tonistiigi from Docker) for both independently discovering this vulnerability, as well as Aleksa Sarai (@cyphar from SUSE) for the original research into this class of security issues and solutions.

Additional thanks go to Tõnis Tiigi for finding some very useful exploit templates for these kinds of race attacks using docker buildx build.

@github-actions
Copy link
Contributor

github-actions bot commented Nov 24, 2025 •
edited
Loading

Outdated

Recommended fixes for image moby/buildkit:buildx-stable-1

Base image is alpine:3

Name3.22.2
Digestsha256:85f2b723e106c34644cd5851d7e81ee87da98ac54672b29947c052a45d31dc2f
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
Pushed1 month ago
Size3.8 MB
Packages20
OS3.22.2
The base image is also available under the supported tag(s): 3.22, 3.22.2, latest

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
3.21
Tag is preferred tag
Also known as:
  • 3.21.5
 Benefits:
  • Image is smaller by 156 KB
  • Minor OS version update
  • Image contains 1 fewer package
  • Tag is preferred tag
  • Tag was pushed more recently
  • Image has same number of vulnerabilities
Image details:
  • Size: 3.6 MB
  • OS: 3.21.5
 1 month ago



1 similar comment
@github-actions
Copy link
Contributor

github-actions bot commented Nov 24, 2025 •
edited
Loading

Outdated

Recommended fixes for image moby/buildkit:buildx-stable-1

Base image is alpine:3

Name3.22.2
Digestsha256:85f2b723e106c34644cd5851d7e81ee87da98ac54672b29947c052a45d31dc2f
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
Pushed1 month ago
Size3.8 MB
Packages20
OS3.22.2
The base image is also available under the supported tag(s): 3.22, 3.22.2, latest

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
3.21
Tag is preferred tag
Also known as:
  • 3.21.5
 Benefits:
  • Image is smaller by 156 KB
  • Minor OS version update
  • Image contains 1 fewer package
  • Tag is preferred tag
  • Tag was pushed more recently
  • Image has same number of vulnerabilities
Image details:
  • Size: 3.6 MB
  • OS: 3.21.5
 1 month ago



@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from bf18914 to 998dd73 Compare December 2, 2025 16:57
@renovate renovate bot changed the title deps(deps): update ansible/ansible-lint action to v25.11.1 deps(deps): update ansible/ansible-lint action to v25.12.0 Dec 2, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2025 •
edited
Loading

Outdated

🔍 Vulnerabilities of moby/buildkit:buildx-stable-1

📦 Image Reference moby/buildkit:buildx-stable-1
digestsha256:fe0990fb85c4586aaa94e599905b75a2676664f065f29bea67ebcd5b2fe88acb
vulnerabilitiescritical: 0 high: 6 medium: 0 low: 0
platformlinux/amd64
size111 MB
packages251
📦 Base Image alpine:3
also known as
  • 3.22
  • 3.22.2
  • af829cb99e2e0ed9843029ba4b20af63bf652e3f57b9aaa049744a8b64d7c608
  • latest
digestsha256:85f2b723e106c34644cd5851d7e81ee87da98ac54672b29947c052a45d31dc2f
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
critical: 0 high: 4 medium: 0 low: 0 stdlib 1.25.0 (golang)

pkg:golang/stdlib@1.25.0

high : CVE--2025--61725

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.026%
EPSS Percentile6th percentile
Description

The ParseAddress function constructeds domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

high : CVE--2025--61723

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.026%
EPSS Percentile6th percentile
Description

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.

This affects programs which parse untrusted PEM inputs.

high : CVE--2025--58188

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.014%
EPSS Percentile2nd percentile
Description

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

high : CVE--2025--58187

Affected range>=1.25.0
<1.25.3
Fixed version1.25.3
EPSS Score0.014%
EPSS Percentile2nd percentile
Description

Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

critical: 0 high: 1 medium: 0 low: 0 github.com/opencontainers/selinux 1.12.0 (golang)

pkg:golang/github.com/opencontainers/selinux@1.12.0

high 7.3: CVE--2025--52881 Race Condition Enabling Link Following

Affected range<=1.12.0
Fixed version1.13.0
CVSS Score7.3
CVSS VectorCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
EPSS Score0.022%
EPSS Percentile5th percentile
Description

Impact

This attack is primarily a more sophisticated version of CVE-2019-19921, which was a flaw which allowed an attacker to trick runc into writing the LSM process labels for a container process into a dummy tmpfs file and thus not apply the correct LSM labels to the container process. The mitigation runc applied for CVE-2019-19921 was fairly limited and effectively only caused runc to verify that when runc writes LSM labels that those labels are actual procfs files.

Rather than using a fake tmpfs file for /proc/self/attr/<label>, an attacker could instead (through various means) make /proc/self/attr/<label> reference a real procfs file, but one that would still be a no-op (such as /proc/self/sched). This would have the same effect but would clear the "is a procfs file" check. Runc is aware that this kind of attack would be possible (even going so far as to discuss this publicly as "future work" at conferences), and runc is working on a far more comprehensive mitigation of this attack, but this security issue was disclosed before runc could complete this work.

In all known versions of runc, an attacker can trick runc into misdirecting writes to /proc to other procfs files through the use of a racing container with shared mounts (runc has also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts.

Note that while /proc/self/attr/<label> was the example used above (which is LSM-specific), this issue affect all writes to /proc in runc and thus also affects sysctls (written to /proc/sys/...) and some other APIs.

Additional Impacts

While investigating this issue, runc discovered that another risk with these redirected writes is that they could be redirected to dangerous files such as /proc/sysrq-trigger rather than just no-op files like /proc/self/sched. For instance, the default AppArmor profile name in Docker is docker-default, which when written to /proc/sysrq-trigger would cause the host system to crash.

When this was discovered, runc conducted an audit of other write operations within runc and found several possible areas where runc could be used as a semi-arbitrary write gadget when combined with the above race attacks. The most concerning attack scenario was the configuration of sysctls. Because the contents of the sysctl are free-form text, an attacker could use a misdirected write to write to /proc/sys/kernel/core_pattern and break out of the container (as described in CVE-2025-31133, kernel upcalls are not namespaced and so coredump helpers will run with complete root privileges on the host). Even if the attacker cannot configure custom sysctls, a valid sysctl string (when redirected to /proc/sysrq-trigger) can easily cause the machine to hang.

Note that the fact that this attack allows you to disable LSM labels makes it a very useful attack to combine with CVE-2025-31133 (as one of the only mitigations available to most users for that issue is AppArmor, and this attack would let you bypass that). However, the misdirected write issue above means that you could also achieve most of the same goals without needing to chain together attacks.

Patches

This advisory is being published as part of a set of three advisories:

  • CVE-2025-31133
  • CVE-2025-52881
  • CVE-2025-52565

The patches fixing this issue have accordingly been combined into a single patchset. The following patches from that patchset resolve the issues in this advisory:

  • db19bbed5348 ("internal/sys: add VerifyInode helper")
  • 6fc191449109 ("internal: move utils.MkdirAllInRoot to internal/pathrs")
  • ff94f9991bd3 ("*: switch to safer securejoin.Reopen")
  • 44a0fcf685db ("go.mod: update to github.com/cyphar/filepath-securejoin@v0.5.0")
  • 77889b56db93 ("internal: add wrappers for securejoin.Proc*")
  • fdcc9d3cad2f ("apparmor: use safe procfs API for labels")
  • ff6fe1324663 ("utils: use safe procfs for /proc/self/fd loop code")
  • b3dd1bc562ed ("utils: remove unneeded EnsureProcHandle")
  • 77d217c7c377 ("init: write sysctls using safe procfs API")
  • 435cc81be6b7 ("init: use securejoin for /proc/self/setgroups")
  • d61fd29d854b ("libct/system: use securejoin for /proc/$pid/stat")
  • 4b37cd93f86e ("libct: align param type for mountCgroupV1/V2 functions")
  • d40b3439a961 ("rootfs: switch to fd-based handling of mountpoint targets")
  • ed6b1693b8b3 ("selinux: use safe procfs API for labels")

    • Please note that this patch includes a private patch for github.com/opencontainers/selinux that could not be made public through a public pull request (as it would necessarily disclose this embargoed security issue).

      The patch includes a complete copy of the forked code and a replace directive (as well as go mod vendor applied), which should still work with downstream build systems. If you cannot apply this patch, you can safely drop it -- some of the other patches in this series should block these kinds of racing mount attacks entirely.

      See selinux: migrate to pathrs-lite procfs API opencontainers/selinux#237 for the upstream patch.

  • 3f925525b44d ("rootfs: re-allow dangling symlinks in mount targets")
  • a41366e74080 ("openat2: improve resilience on busy systems")

runc 1.2.8, 1.3.3, and 1.4.0-rc.3 have been released and all contain fixes for these issues. As per runc's new release model, runc 1.1.x and earlier are no longer supported and thus have not been patched.

Mitigations

  • Do not run untrusted container images from unknown or unverified sources.

  • For the basic no-op attack, this attack allows a container process to run with the same LSM labels as runc. For most AppArmor deployments this means it will be unconfined, and for SELinux it will likely be container_runtime_t. Runc has not conducted in-depth testing of the impact on SELinux -- it is possible that it provides some reasonable protection but it seems likely that an attacker could cause harm to systems even with such an SELinux setup.

  • For the more involved redirect and write gadget attacks, unfortunately most LSM profiles (including the standard container-selinux profiles) provide the container runtime access to sysctl files (including /proc/sysrq-trigger) and so LSMs likely do not provide much protection against these attacks.

  • Using rootless containers provides some protection against these kinds of bugs (privileged writes in runc being redirected) -- by having runc itself be an unprivileged process, in general you would expect the impact scope of a runc bug to be less severe as it would only have the privileges afforded to the host user which spawned runc. For this particular bug, the privilege escalation caused by the inadvertent write issue is entirely mitigated with rootless containers because the unprivileged user that the runc process is executing as cannot write to the aforementioned procfs files (even intentionally).

Other Runtimes

As this vulnerability boils down to a fairly easy-to-make logic bug, runc has provided information to other OCI (crun, youki) and non-OCI (LXC) container runtimes about this vulnerability.

Based on discussions with other runtimes, it seems that crun and youki may have similar security issues and will release a co-ordinated security release along with runc. LXC appears to use the host's /proc for all procfs operations, and so is likely not vulnerable to this issue (this is a trade-off -- runc uses the container's procfs to avoid CVE-2016-9962-style attacks).

Credits

Thanks to Li Fubang (@lifubang from acmcoder.com, CIIC) and Tõnis Tiigi (@tonistiigi from Docker) for both independently discovering this vulnerability, as well as Aleksa Sarai (@cyphar from SUSE) for the original research into this class of security issues and solutions.

Additional thanks go to Tõnis Tiigi for finding some very useful exploit templates for these kinds of race attacks using docker buildx build.

critical: 0 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.42.0 (golang)

pkg:golang/golang.org/x/crypto@0.42.0

high : CVE--2025--47913

Affected range<0.43.0
Fixed version0.43.0
EPSS Score0.018%
EPSS Percentile3rd percentile
Description

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2025 •
edited
Loading

Outdated

Recommended fixes for image moby/buildkit:buildx-stable-1

Base image is alpine:3

Name3.22.2
Digestsha256:85f2b723e106c34644cd5851d7e81ee87da98ac54672b29947c052a45d31dc2f
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
Pushed1 month ago
Size3.8 MB
Packages20
OS3.22.2
The base image is also available under the supported tag(s): 3.22, 3.22.2, latest

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
3.21
Tag is preferred tag
Also known as:
  • 3.21.5
 Benefits:
  • Image is smaller by 156 KB
  • Minor OS version update
  • Image contains 1 fewer package
  • Tag is preferred tag
  • Tag was pushed more recently
  • Image has same number of vulnerabilities
Image details:
  • Size: 3.6 MB
  • OS: 3.21.5
 1 month ago



@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2025

🔍 Vulnerabilities of moby/buildkit:buildx-stable-1

📦 Image Reference moby/buildkit:buildx-stable-1
digestsha256:fe0990fb85c4586aaa94e599905b75a2676664f065f29bea67ebcd5b2fe88acb
vulnerabilitiescritical: 0 high: 6 medium: 0 low: 0
platformlinux/amd64
size111 MB
packages251
📦 Base Image alpine:3
also known as
  • 3.22
  • 3.22.2
  • af829cb99e2e0ed9843029ba4b20af63bf652e3f57b9aaa049744a8b64d7c608
  • latest
digestsha256:85f2b723e106c34644cd5851d7e81ee87da98ac54672b29947c052a45d31dc2f
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
critical: 0 high: 4 medium: 0 low: 0 stdlib 1.25.0 (golang)

pkg:golang/stdlib@1.25.0

high : CVE--2025--61725

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.026%
EPSS Percentile6th percentile
Description

The ParseAddress function constructeds domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.

high : CVE--2025--61723

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.026%
EPSS Percentile6th percentile
Description

The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.

This affects programs which parse untrusted PEM inputs.

high : CVE--2025--58188

Affected range>=1.25.0
<1.25.2
Fixed version1.25.2
EPSS Score0.014%
EPSS Percentile2nd percentile
Description

Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.

This affects programs which validate arbitrary certificate chains.

high : CVE--2025--58187

Affected range>=1.25.0
<1.25.3
Fixed version1.25.3
EPSS Score0.014%
EPSS Percentile2nd percentile
Description

Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate.

This affects programs which validate arbitrary certificate chains.

critical: 0 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.42.0 (golang)

pkg:golang/golang.org/x/crypto@0.42.0

high : CVE--2025--47913

Affected range<0.43.0
Fixed version0.43.0
EPSS Score0.018%
EPSS Percentile3rd percentile
Description

SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.

critical: 0 high: 1 medium: 0 low: 0 github.com/opencontainers/selinux 1.12.0 (golang)

pkg:golang/github.com/opencontainers/selinux@1.12.0

high 7.3: CVE--2025--52881 Race Condition Enabling Link Following

Affected range<=1.12.0
Fixed version1.13.0
CVSS Score7.3
CVSS VectorCVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
EPSS Score0.022%
EPSS Percentile5th percentile
Description

Impact

This attack is primarily a more sophisticated version of CVE-2019-19921, which was a flaw which allowed an attacker to trick runc into writing the LSM process labels for a container process into a dummy tmpfs file and thus not apply the correct LSM labels to the container process. The mitigation runc applied for CVE-2019-19921 was fairly limited and effectively only caused runc to verify that when runc writes LSM labels that those labels are actual procfs files.

Rather than using a fake tmpfs file for /proc/self/attr/<label>, an attacker could instead (through various means) make /proc/self/attr/<label> reference a real procfs file, but one that would still be a no-op (such as /proc/self/sched). This would have the same effect but would clear the "is a procfs file" check. Runc is aware that this kind of attack would be possible (even going so far as to discuss this publicly as "future work" at conferences), and runc is working on a far more comprehensive mitigation of this attack, but this security issue was disclosed before runc could complete this work.

In all known versions of runc, an attacker can trick runc into misdirecting writes to /proc to other procfs files through the use of a racing container with shared mounts (runc has also verified this attack is possible to exploit using a standard Dockerfile with docker buildx build as that also permits triggering parallel execution of containers with custom shared mounts configured). This redirect could be through symbolic links in a tmpfs or theoretically other methods such as regular bind-mounts.

Note that while /proc/self/attr/<label> was the example used above (which is LSM-specific), this issue affect all writes to /proc in runc and thus also affects sysctls (written to /proc/sys/...) and some other APIs.

Additional Impacts

While investigating this issue, runc discovered that another risk with these redirected writes is that they could be redirected to dangerous files such as /proc/sysrq-trigger rather than just no-op files like /proc/self/sched. For instance, the default AppArmor profile name in Docker is docker-default, which when written to /proc/sysrq-trigger would cause the host system to crash.

When this was discovered, runc conducted an audit of other write operations within runc and found several possible areas where runc could be used as a semi-arbitrary write gadget when combined with the above race attacks. The most concerning attack scenario was the configuration of sysctls. Because the contents of the sysctl are free-form text, an attacker could use a misdirected write to write to /proc/sys/kernel/core_pattern and break out of the container (as described in CVE-2025-31133, kernel upcalls are not namespaced and so coredump helpers will run with complete root privileges on the host). Even if the attacker cannot configure custom sysctls, a valid sysctl string (when redirected to /proc/sysrq-trigger) can easily cause the machine to hang.

Note that the fact that this attack allows you to disable LSM labels makes it a very useful attack to combine with CVE-2025-31133 (as one of the only mitigations available to most users for that issue is AppArmor, and this attack would let you bypass that). However, the misdirected write issue above means that you could also achieve most of the same goals without needing to chain together attacks.

Patches

This advisory is being published as part of a set of three advisories:

  • CVE-2025-31133
  • CVE-2025-52881
  • CVE-2025-52565

The patches fixing this issue have accordingly been combined into a single patchset. The following patches from that patchset resolve the issues in this advisory:

  • db19bbed5348 ("internal/sys: add VerifyInode helper")
  • 6fc191449109 ("internal: move utils.MkdirAllInRoot to internal/pathrs")
  • ff94f9991bd3 ("*: switch to safer securejoin.Reopen")
  • 44a0fcf685db ("go.mod: update to github.com/cyphar/filepath-securejoin@v0.5.0")
  • 77889b56db93 ("internal: add wrappers for securejoin.Proc*")
  • fdcc9d3cad2f ("apparmor: use safe procfs API for labels")
  • ff6fe1324663 ("utils: use safe procfs for /proc/self/fd loop code")
  • b3dd1bc562ed ("utils: remove unneeded EnsureProcHandle")
  • 77d217c7c377 ("init: write sysctls using safe procfs API")
  • 435cc81be6b7 ("init: use securejoin for /proc/self/setgroups")
  • d61fd29d854b ("libct/system: use securejoin for /proc/$pid/stat")
  • 4b37cd93f86e ("libct: align param type for mountCgroupV1/V2 functions")
  • d40b3439a961 ("rootfs: switch to fd-based handling of mountpoint targets")
  • ed6b1693b8b3 ("selinux: use safe procfs API for labels")

    • Please note that this patch includes a private patch for github.com/opencontainers/selinux that could not be made public through a public pull request (as it would necessarily disclose this embargoed security issue).

      The patch includes a complete copy of the forked code and a replace directive (as well as go mod vendor applied), which should still work with downstream build systems. If you cannot apply this patch, you can safely drop it -- some of the other patches in this series should block these kinds of racing mount attacks entirely.

      See selinux: migrate to pathrs-lite procfs API opencontainers/selinux#237 for the upstream patch.

  • 3f925525b44d ("rootfs: re-allow dangling symlinks in mount targets")
  • a41366e74080 ("openat2: improve resilience on busy systems")

runc 1.2.8, 1.3.3, and 1.4.0-rc.3 have been released and all contain fixes for these issues. As per runc's new release model, runc 1.1.x and earlier are no longer supported and thus have not been patched.

Mitigations

  • Do not run untrusted container images from unknown or unverified sources.

  • For the basic no-op attack, this attack allows a container process to run with the same LSM labels as runc. For most AppArmor deployments this means it will be unconfined, and for SELinux it will likely be container_runtime_t. Runc has not conducted in-depth testing of the impact on SELinux -- it is possible that it provides some reasonable protection but it seems likely that an attacker could cause harm to systems even with such an SELinux setup.

  • For the more involved redirect and write gadget attacks, unfortunately most LSM profiles (including the standard container-selinux profiles) provide the container runtime access to sysctl files (including /proc/sysrq-trigger) and so LSMs likely do not provide much protection against these attacks.

  • Using rootless containers provides some protection against these kinds of bugs (privileged writes in runc being redirected) -- by having runc itself be an unprivileged process, in general you would expect the impact scope of a runc bug to be less severe as it would only have the privileges afforded to the host user which spawned runc. For this particular bug, the privilege escalation caused by the inadvertent write issue is entirely mitigated with rootless containers because the unprivileged user that the runc process is executing as cannot write to the aforementioned procfs files (even intentionally).

Other Runtimes

As this vulnerability boils down to a fairly easy-to-make logic bug, runc has provided information to other OCI (crun, youki) and non-OCI (LXC) container runtimes about this vulnerability.

Based on discussions with other runtimes, it seems that crun and youki may have similar security issues and will release a co-ordinated security release along with runc. LXC appears to use the host's /proc for all procfs operations, and so is likely not vulnerable to this issue (this is a trade-off -- runc uses the container's procfs to avoid CVE-2016-9962-style attacks).

Credits

Thanks to Li Fubang (@lifubang from acmcoder.com, CIIC) and Tõnis Tiigi (@tonistiigi from Docker) for both independently discovering this vulnerability, as well as Aleksa Sarai (@cyphar from SUSE) for the original research into this class of security issues and solutions.

Additional thanks go to Tõnis Tiigi for finding some very useful exploit templates for these kinds of race attacks using docker buildx build.

@github-actions
Copy link
Contributor

github-actions bot commented Dec 2, 2025

Recommended fixes for image moby/buildkit:buildx-stable-1

Base image is alpine:3

Name3.22.2
Digestsha256:85f2b723e106c34644cd5851d7e81ee87da98ac54672b29947c052a45d31dc2f
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 2
Pushed1 month ago
Size3.8 MB
Packages20
OS3.22.2
The base image is also available under the supported tag(s): 3.22, 3.22.2, latest

Refresh base image

Rebuild the image using a newer base image version. Updating this may result in breaking changes.

✅ This image version is up to date.

Change base image

TagDetailsPushedVulnerabilities
3.21
Tag is preferred tag
Also known as:
  • 3.21.5
 Benefits:
  • Image is smaller by 156 KB
  • Minor OS version update
  • Image contains 1 fewer package
  • Tag is preferred tag
  • Tag was pushed more recently
  • Image has same number of vulnerabilities
Image details:
  • Size: 3.6 MB
  • OS: 3.21.5
 1 month ago



Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@lotyp lotyp Awaiting requested review from lotyp lotyp is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

type: maintenance For maintenance, refactor and testing (perf, chore, style, revert, refactor, test, build, ci)

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant