Skip to content

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

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 #110

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 enabled auto-merge (squash) July 29, 2025 23:02
@renovate renovate bot requested a review from lotyp as a code owner July 29, 2025 23:02
@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

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:d90e88506afe190999ea6ce16329d614408a9bb4e5d0f29030c5d7f6fbac1c8c
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size108 MB
packages247
📦 Base Image php:56992578823268ea128fe278fd23c5b82fefe8c76bb67ecaaaded5d3bfc89101
also known as
  • 8.1-alpine
  • 8.1-alpine3.21
  • 8.1-cli-alpine
  • 8.1-cli-alpine3.21
  • 8.1.33-alpine
  • 8.1.33-alpine3.21
  • 8.1.33-cli-alpine
  • 8.1.33-cli-alpine3.21
digestsha256:b354796211589037af228ef6aa3a7663b6b8e8cee9e11aa317f5b260afb9b9f8
vulnerabilitiescritical: 0 high: 1 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 1 medium: 0 low: 0 sqlite 3.48.0-r2 (apk)

pkg:apk/alpine/sqlite@3.48.0-r2?os_name=alpine&os_version=3.21

high : CVE--2025--6965

Affected range<3.48.0-r3
Fixed version3.48.0-r3
EPSS Score0.047%
EPSS Percentile14th percentile
Description

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:3c93d4bdd1e7d8be8db566fe4c5c17b8a097c606f35fbe5f828806dee41ad0c4
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size126 MB
packages265
📦 Base Image php:56992578823268ea128fe278fd23c5b82fefe8c76bb67ecaaaded5d3bfc89101
also known as
  • 8.1-alpine
  • 8.1-alpine3.21
  • 8.1-cli-alpine
  • 8.1-cli-alpine3.21
  • 8.1.33-alpine
  • 8.1.33-alpine3.21
  • 8.1.33-cli-alpine
  • 8.1.33-cli-alpine3.21
digestsha256:b354796211589037af228ef6aa3a7663b6b8e8cee9e11aa317f5b260afb9b9f8
vulnerabilitiescritical: 0 high: 1 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 1 medium: 0 low: 0 setuptools 70.3.0 (pypi)

pkg:pypi/setuptools@70.3.0

high 7.7: CVE--2025--47273 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Affected range<78.1.1
Fixed version78.1.1
CVSS Score7.7
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P
EPSS Score0.139%
EPSS Percentile35th percentile
Description

Summary

A path traversal vulnerability in PackageIndex was fixed in setuptools version 78.1.1

Details

    def _download_url(self, url, tmpdir):
        # Determine download filename
        #
        name, _fragment = egg_info_for_url(url)
        if name:
            while '..' in name:
                name = name.replace('..', '.').replace('\\', '_')
        else:
            name = "__downloaded__"  # default if URL has no path contents

        if name.endswith('.[egg.zip](http://egg.zip/)'):
            name = name[:-4]  # strip the extra .zip before download

 -->       filename = os.path.join(tmpdir, name)

Here: https://github.com/pypa/setuptools/blob/6ead555c5fb29bc57fe6105b1bffc163f56fd558/setuptools/package_index.py#L810C1-L825C88

os.path.join() discards the first argument tmpdir if the second begins with a slash or drive letter.
name is derived from a URL without sufficient sanitization. While there is some attempt to sanitize by replacing instances of '..' with '.', it is insufficient.

Risk Assessment

As easy_install and package_index are deprecated, the exploitation surface is reduced.
However, it seems this could be exploited in a similar fashion like GHSA-r9hx-vwmv-q579, and as described by POC 4 in GHSA-cx63-2mw6-8hw5 report: via malicious URLs present on the pages of a package index.

Impact

An attacker would be allowed to write files to arbitrary locations on the filesystem with the permissions of the process running the Python code, which could escalate to RCE depending on the context.

References

https://huntr.com/bounties/d6362117-ad57-4e83-951f-b8141c6e7ca5
pypa/setuptools#4946

critical: 0 high: 1 medium: 0 low: 0 sqlite 3.48.0-r2 (apk)

pkg:apk/alpine/sqlite@3.48.0-r2?os_name=alpine&os_version=3.21

high : CVE--2025--6965

Affected range<3.48.0-r3
Fixed version3.48.0-r3
EPSS Score0.047%
EPSS Percentile14th percentile
Description

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:5a5fb295fac3c99f76492e0c2c1aad0316300823f5bab2ee09515e4b706a83fd
vulnerabilitiescritical: 1 high: 7 medium: 0 low: 0
platformlinux/amd64
size108 MB
packages250
📦 Base Image php:6895d0713f94121218fde3d48d359ad6a829ce6fcf3e8606f1514e04bca3d2be
also known as
  • 8.3-fpm-alpine
  • 8.3-fpm-alpine3.22
  • 8.3.23-fpm-alpine
  • 8.3.23-fpm-alpine3.22
digestsha256:6d134d3d8edf3f9468cbc8de6489b942f0340914cc6c7bc00018ea838abdc5c4
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 5 medium: 0 low: 0 git 2.49.1-r0 (apk)

pkg:apk/alpine/git@2.49.1-r0?os_name=alpine&os_version=3.22

high : CVE--2025--48385

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.102%
EPSS Percentile29th percentile
Description

high : CVE--2025--46334

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.021%
EPSS Percentile4th percentile
Description

high : CVE--2025--27614

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--46835

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--48384

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.016%
EPSS Percentile2nd percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.1-alpine

Name8.1.33-alpine3.21
Digestsha256:b354796211589037af228ef6aa3a7663b6b8e8cee9e11aa317f5b260afb9b9f8
Vulnerabilitiescritical: 0 high: 1 medium: 0 low: 0
Pushed3 weeks ago
Size36 MB
Packages59
Flavoralpine
OS3.21
Runtime8.1.33
The base image is also available under the supported tag(s): 8.1-alpine3.21, 8.1-cli-alpine, 8.1-cli-alpine3.21, 8.1.33-alpine, 8.1.33-alpine3.21, 8.1.33-cli-alpine, 8.1.33-cli-alpine3.21

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
8.1-alpine3.22
Patch runtime version update
Also known as:
  • 8.1.33-cli-alpine3.22
  • 8.1-cli-alpine3.22
  • 8.1.33-alpine3.22
 Benefits:
  • Patch runtime version update
  • Same OS detected
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.1.33
 3 weeks ago



8.3-alpine
Minor runtime version update
Also known as:
  • 8.3.23-cli-alpine
  • 8.3.23-cli-alpine3.22
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.22
  • 8.3.23-alpine
  • 8.3.23-alpine3.22
  • 8.3-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Tag was pushed more recently
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.23
 3 weeks ago



8.3-alpine3.21
Minor runtime version update
Also known as:
  • 8.3.23-cli-alpine3.21
  • 8.3-cli-alpine3.21
  • 8.3.23-alpine3.21
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.3.23
 3 weeks ago



8.4-alpine3.21
Minor runtime version update
Also known as:
  • 8.4.10-cli-alpine3.21
  • 8-cli-alpine3.21
  • cli-alpine3.21
  • alpine3.21
  • 8.4.10-alpine3.21
  • 8-alpine3.21
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.4.10
 3 weeks ago



8.4-alpine
Minor runtime version update
Also known as:
  • 8.4.10-cli-alpine
  • 8.4.10-cli-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • cli-alpine
  • cli-alpine3.22
  • alpine
  • alpine3.22
  • 8.4-alpine3.22
  • 8-alpine
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4
 3 weeks ago



8.2-alpine
Minor runtime version update
Also known as:
  • 8.2.29-cli-alpine
  • 8.2.29-cli-alpine3.22
  • 8.2-cli-alpine
  • 8.2-cli-alpine3.22
  • 8.2.29-alpine
  • 8.2.29-alpine3.22
  • 8.2-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
  • 8.2-alpine was pulled 1.8K times last month
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.2.29
 3 weeks ago



8.2-alpine3.21
Minor runtime version update
Also known as:
  • 8.2.29-cli-alpine3.21
  • 8.2-cli-alpine3.21
  • 8.2.29-alpine3.21
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.2.29
 3 weeks ago



8.4.10-alpine
Minor runtime version update
Also known as:
  • 8.4.10-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.10
 3 weeks ago



1 similar comment
@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.1-alpine

Name8.1.33-alpine3.21
Digestsha256:b354796211589037af228ef6aa3a7663b6b8e8cee9e11aa317f5b260afb9b9f8
Vulnerabilitiescritical: 0 high: 1 medium: 0 low: 0
Pushed3 weeks ago
Size36 MB
Packages59
Flavoralpine
OS3.21
Runtime8.1.33
The base image is also available under the supported tag(s): 8.1-alpine3.21, 8.1-cli-alpine, 8.1-cli-alpine3.21, 8.1.33-alpine, 8.1.33-alpine3.21, 8.1.33-cli-alpine, 8.1.33-cli-alpine3.21

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
8.1-alpine3.22
Patch runtime version update
Also known as:
  • 8.1.33-cli-alpine3.22
  • 8.1-cli-alpine3.22
  • 8.1.33-alpine3.22
 Benefits:
  • Patch runtime version update
  • Same OS detected
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.1.33
 3 weeks ago



8.3-alpine
Minor runtime version update
Also known as:
  • 8.3.23-cli-alpine
  • 8.3.23-cli-alpine3.22
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.22
  • 8.3.23-alpine
  • 8.3.23-alpine3.22
  • 8.3-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Tag was pushed more recently
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.23
 3 weeks ago



8.3-alpine3.21
Minor runtime version update
Also known as:
  • 8.3.23-cli-alpine3.21
  • 8.3-cli-alpine3.21
  • 8.3.23-alpine3.21
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.3.23
 3 weeks ago



8.4-alpine3.21
Minor runtime version update
Also known as:
  • 8.4.10-cli-alpine3.21
  • 8-cli-alpine3.21
  • cli-alpine3.21
  • alpine3.21
  • 8.4.10-alpine3.21
  • 8-alpine3.21
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.4.10
 3 weeks ago



8.4-alpine
Minor runtime version update
Also known as:
  • 8.4.10-cli-alpine
  • 8.4.10-cli-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • cli-alpine
  • cli-alpine3.22
  • alpine
  • alpine3.22
  • 8.4-alpine3.22
  • 8-alpine
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4
 3 weeks ago



8.2-alpine
Minor runtime version update
Also known as:
  • 8.2.29-cli-alpine
  • 8.2.29-cli-alpine3.22
  • 8.2-cli-alpine
  • 8.2-cli-alpine3.22
  • 8.2.29-alpine
  • 8.2.29-alpine3.22
  • 8.2-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
  • 8.2-alpine was pulled 1.8K times last month
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.2.29
 3 weeks ago



8.2-alpine3.21
Minor runtime version update
Also known as:
  • 8.2.29-cli-alpine3.21
  • 8.2-cli-alpine3.21
  • 8.2.29-alpine3.21
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.2.29
 3 weeks ago



8.4.10-alpine
Minor runtime version update
Also known as:
  • 8.4.10-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.10
 3 weeks ago



@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-fpm-alpine

Name8.3.23-fpm-alpine3.22
Digestsha256:6d134d3d8edf3f9468cbc8de6489b942f0340914cc6c7bc00018ea838abdc5c4
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed3 weeks ago
Size33 MB
Packages61
Flavoralpine
OS3.22
Runtime8.3.23
The base image is also available under the supported tag(s): 8.3-fpm-alpine3.22, 8.3.23-fpm-alpine, 8.3.23-fpm-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
8.4-fpm-alpine
Image has same number of vulnerabilities
Also known as:
  • 8.4.10-fpm-alpine
  • 8.4.10-fpm-alpine3.22
  • 8.4-fpm-alpine3.22
  • 8-fpm-alpine
  • 8-fpm-alpine3.22
  • fpm-alpine
  • fpm-alpine3.22
 Benefits:
  • Same OS detected
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
 3 weeks ago



@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:40ee331dd6c3dbfe7a5b21a1aeb5146cab888e144c213e653263423418368998
vulnerabilitiescritical: 1 high: 7 medium: 0 low: 0
platformlinux/amd64
size131 MB
packages284
📦 Base Image php:37c03f5427764bbf4b1d18e24034c2bef66d53588079fb3a90d140d341f28cd8
also known as
  • 8.3-alpine
  • 8.3-alpine3.22
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.22
  • 8.3.23-alpine
  • 8.3.23-alpine3.22
  • 8.3.23-cli-alpine
  • 8.3.23-cli-alpine3.22
digestsha256:7c4b34b9bcea402f1fedb8985a6c6d49f1283c26a76f432088f6a23f744fc194
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 5 medium: 0 low: 0 git 2.49.1-r0 (apk)

pkg:apk/alpine/git@2.49.1-r0?os_name=alpine&os_version=3.22

high : CVE--2025--48385

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.102%
EPSS Percentile29th percentile
Description

high : CVE--2025--46334

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.021%
EPSS Percentile4th percentile
Description

high : CVE--2025--27614

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--46835

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--48384

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.016%
EPSS Percentile2nd percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:760b967584396fd8c0aefab591097a9ec8e0157da2be9862a6e00b48628bea3e
vulnerabilitiescritical: 1 high: 7 medium: 0 low: 0
platformlinux/amd64
size112 MB
packages249
📦 Base Image php:37c03f5427764bbf4b1d18e24034c2bef66d53588079fb3a90d140d341f28cd8
also known as
  • 8.3-alpine
  • 8.3-alpine3.22
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.22
  • 8.3.23-alpine
  • 8.3.23-alpine3.22
  • 8.3.23-cli-alpine
  • 8.3.23-cli-alpine3.22
digestsha256:7c4b34b9bcea402f1fedb8985a6c6d49f1283c26a76f432088f6a23f744fc194
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 5 medium: 0 low: 0 git 2.49.1-r0 (apk)

pkg:apk/alpine/git@2.49.1-r0?os_name=alpine&os_version=3.22

high : CVE--2025--48385

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.102%
EPSS Percentile29th percentile
Description

high : CVE--2025--46334

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.021%
EPSS Percentile4th percentile
Description

high : CVE--2025--27614

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--46835

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--48384

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.016%
EPSS Percentile2nd percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-alpine

Name8.3.23-alpine3.22
Digestsha256:7c4b34b9bcea402f1fedb8985a6c6d49f1283c26a76f432088f6a23f744fc194
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed3 weeks ago
Size37 MB
Packages60
Flavoralpine
OS3.22
Runtime8.3.23
The base image is also available under the supported tag(s): 8.3-alpine3.22, 8.3-cli-alpine, 8.3-cli-alpine3.22, 8.3.23-alpine, 8.3.23-alpine3.22, 8.3.23-cli-alpine, 8.3.23-cli-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
8.4.10-alpine
Minor runtime version update
Also known as:
  • 8.4.10-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.10
 3 weeks ago



8.4-alpine
Minor runtime version update
Also known as:
  • 8.4.10-cli-alpine
  • 8.4.10-cli-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • cli-alpine
  • cli-alpine3.22
  • alpine
  • alpine3.22
  • 8.4-alpine3.22
  • 8-alpine
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4
 3 weeks ago



@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:cc401107563b79259c3f55a9dd7300d8877efa5807c62b1ead81e4586794c9c6
vulnerabilitiescritical: 1 high: 7 medium: 0 low: 0
platformlinux/amd64
size112 MB
packages250
📦 Base Image oisupport/staging-amd64:8-fpm-alpine
also known as
  • 8-fpm-alpine3.22
  • 8.4-fpm-alpine
  • 8.4-fpm-alpine3.22
  • 8.4.10-fpm-alpine
  • 8.4.10-fpm-alpine3.22
  • bf3abc5b8cece0c8377d2b43fda020363802e516010bb9b7bd2dc65d89953a21
  • fpm-alpine
  • fpm-alpine3.22
digestsha256:8f5c6041134df87721b8767876198c72504bb3c2c56b028eba3110a5aedcc948
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 5 medium: 0 low: 0 git 2.49.1-r0 (apk)

pkg:apk/alpine/git@2.49.1-r0?os_name=alpine&os_version=3.22

high : CVE--2025--48385

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.102%
EPSS Percentile29th percentile
Description

high : CVE--2025--46334

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.021%
EPSS Percentile4th percentile
Description

high : CVE--2025--27614

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--46835

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--48384

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.016%
EPSS Percentile2nd percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:c0eb08d3ecd7ff5376ab13c1d3dd058f1e3d2d197fd4cb0400960e2eefdc6209
vulnerabilitiescritical: 1 high: 7 medium: 0 low: 0
platformlinux/amd64
size111 MB
packages249
📦 Base Image oisupport/staging-amd64:6d8f1501134a9bdee714377c21301b62cf07f86c3b82a73ae27b779d30916fdb
also known as
  • 8.2-alpine
  • 8.2-alpine3.22
  • 8.2-cli-alpine
  • 8.2-cli-alpine3.22
  • 8.2.29-alpine
  • 8.2.29-alpine3.22
  • 8.2.29-cli-alpine
  • 8.2.29-cli-alpine3.22
digestsha256:53ac6edeae46bbdd44555b8be8d0823f7d212c8c8e725439fbdbe1d1ad3e53ac
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 5 medium: 0 low: 0 git 2.49.1-r0 (apk)

pkg:apk/alpine/git@2.49.1-r0?os_name=alpine&os_version=3.22

high : CVE--2025--48385

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.102%
EPSS Percentile29th percentile
Description

high : CVE--2025--46334

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.021%
EPSS Percentile4th percentile
Description

high : CVE--2025--27614

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--46835

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--48384

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.016%
EPSS Percentile2nd percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-alpine

Name8.3.23-alpine3.22
Digestsha256:7c4b34b9bcea402f1fedb8985a6c6d49f1283c26a76f432088f6a23f744fc194
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed3 weeks ago
Size37 MB
Packages60
Flavoralpine
OS3.22
Runtime8.3.23
The base image is also available under the supported tag(s): 8.3-alpine3.22, 8.3-cli-alpine, 8.3-cli-alpine3.22, 8.3.23-alpine, 8.3.23-alpine3.22, 8.3.23-cli-alpine, 8.3.23-cli-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
8.4.10-alpine
Minor runtime version update
Also known as:
  • 8.4.10-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.10
 3 weeks ago



8.4-alpine
Minor runtime version update
Also known as:
  • 8.4.10-cli-alpine
  • 8.4.10-cli-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • cli-alpine
  • cli-alpine3.22
  • alpine
  • alpine3.22
  • 8.4-alpine3.22
  • 8-alpine
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 42 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4
 3 weeks ago



@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is :6d8f1501134a9bdee714377c21301b62cf07f86c3b82a73ae27b779d30916fdb

Digest
Vulnerabilities
Size0 B
Packages0

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

✅ There are no tag recommendations at this time.

@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is :8-fpm-alpine

Digest
Vulnerabilities
Size0 B
Packages0

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

✅ There are no tag recommendations at this time.

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:201bbb9b530f56899dc8e598e8ecb14286f9edd3d7828c37bd721392ad9f999e
vulnerabilitiescritical: 1 high: 7 medium: 0 low: 0
platformlinux/amd64
size131 MB
packages284
📦 Base Image oisupport/staging-amd64:6d8f1501134a9bdee714377c21301b62cf07f86c3b82a73ae27b779d30916fdb
also known as
  • 8.2-alpine
  • 8.2-alpine3.22
  • 8.2-cli-alpine
  • 8.2-cli-alpine3.22
  • 8.2.29-alpine
  • 8.2.29-alpine3.22
  • 8.2.29-cli-alpine
  • 8.2.29-cli-alpine3.22
digestsha256:53ac6edeae46bbdd44555b8be8d0823f7d212c8c8e725439fbdbe1d1ad3e53ac
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 5 medium: 0 low: 0 git 2.49.1-r0 (apk)

pkg:apk/alpine/git@2.49.1-r0?os_name=alpine&os_version=3.22

high : CVE--2025--48385

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.102%
EPSS Percentile29th percentile
Description

high : CVE--2025--46334

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.021%
EPSS Percentile4th percentile
Description

high : CVE--2025--27614

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--46835

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--48384

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.016%
EPSS Percentile2nd percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:1ca69f0c21fd357e4c27dd54311ce01d7f07b5ecff6c437b66b18f065a19c658
vulnerabilitiescritical: 1 high: 7 medium: 0 low: 0
platformlinux/amd64
size136 MB
packages284
📦 Base Image php:8-alpine
also known as
  • 8-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • 8.4-alpine
  • 8.4-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8.4.10-cli-alpine
  • 8.4.10-cli-alpine3.22
  • 9ff1d89ef9c2fb92353d89f7d4acd209fa736d8eb62a53b9ba0d93dd408e60af
  • alpine
  • alpine3.22
  • cli-alpine
  • cli-alpine3.22
digestsha256:f5f0e78475a1280bb8f4a77fa426fbfc2390f418f51757359949cb8ebf79cc52
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 5 medium: 0 low: 0 git 2.49.1-r0 (apk)

pkg:apk/alpine/git@2.49.1-r0?os_name=alpine&os_version=3.22

high : CVE--2025--48385

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.102%
EPSS Percentile29th percentile
Description

high : CVE--2025--46334

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.021%
EPSS Percentile4th percentile
Description

high : CVE--2025--27614

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--46835

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--48384

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.016%
EPSS Percentile2nd percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:72a8429ae547e080e91aaeb51d14891bff7082c04bfe90421f65ad8cfca93dbb
vulnerabilitiescritical: 1 high: 7 medium: 0 low: 0
platformlinux/amd64
size117 MB
packages249
📦 Base Image php:8-alpine
also known as
  • 8-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • 8.4-alpine
  • 8.4-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8.4.10-cli-alpine
  • 8.4.10-cli-alpine3.22
  • 9ff1d89ef9c2fb92353d89f7d4acd209fa736d8eb62a53b9ba0d93dd408e60af
  • alpine
  • alpine3.22
  • cli-alpine
  • cli-alpine3.22
digestsha256:f5f0e78475a1280bb8f4a77fa426fbfc2390f418f51757359949cb8ebf79cc52
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 5 medium: 0 low: 0 git 2.49.1-r0 (apk)

pkg:apk/alpine/git@2.49.1-r0?os_name=alpine&os_version=3.22

high : CVE--2025--48385

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.102%
EPSS Percentile29th percentile
Description

high : CVE--2025--46334

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.021%
EPSS Percentile4th percentile
Description

high : CVE--2025--27614

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--46835

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--48384

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.016%
EPSS Percentile2nd percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is :6d8f1501134a9bdee714377c21301b62cf07f86c3b82a73ae27b779d30916fdb

Digest
Vulnerabilities
Size0 B
Packages0

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

✅ There are no tag recommendations at this time.

@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8-alpine

Name8.4-alpine3.22
Digestsha256:f5f0e78475a1280bb8f4a77fa426fbfc2390f418f51757359949cb8ebf79cc52
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed3 weeks ago
Size42 MB
Packages60
Flavoralpine
OS3.22
Runtime8.4
The base image is also available under the supported tag(s): 8-alpine3.22, 8-cli-alpine, 8-cli-alpine3.22, 8.4-alpine, 8.4-alpine3.22, 8.4-cli-alpine, 8.4-cli-alpine3.22, 8.4.10-cli-alpine, 8.4.10-cli-alpine3.22, alpine, alpine3.22, cli-alpine, cli-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
8.4.10-alpine
Minor runtime version update
Also known as:
  • 8.4.10-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.10
 3 weeks ago



@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:eeb718f6744451d82025208550a3e70ede2e369e045f023385fdaab5c9329e38
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size104 MB
packages248
📦 Base Image php:46b1fe80d62af9bafc4eeecf942c85ac59df475fed0d5c6c00ad4a5e86abd8c8
also known as
  • 8.1-fpm-alpine
  • 8.1-fpm-alpine3.21
  • 8.1.33-fpm-alpine
  • 8.1.33-fpm-alpine3.21
digestsha256:5871d3d4f16880e00a32bd2ed082d37eccc1e79473014df282c8d9207b940cb0
vulnerabilitiescritical: 0 high: 1 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 1 medium: 0 low: 0 sqlite 3.48.0-r2 (apk)

pkg:apk/alpine/sqlite@3.48.0-r2?os_name=alpine&os_version=3.21

high : CVE--2025--6965

Affected range<3.48.0-r3
Fixed version3.48.0-r3
EPSS Score0.047%
EPSS Percentile14th percentile
Description

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:db5ad972c8b86fc5cc38e810077c3de74711e209bf3b81bad51cdb6744a674f5
vulnerabilitiescritical: 1 high: 7 medium: 0 low: 0
platformlinux/amd64
size107 MB
packages250
📦 Base Image php:640a89f12d2b0873fd58016ba9a2ad6e9daf3c0ef46fec05a5a0f301799a87cf
also known as
  • 8.2-fpm-alpine
  • 8.2-fpm-alpine3.22
  • 8.2.29-fpm-alpine
  • 8.2.29-fpm-alpine3.22
digestsha256:aaccb621d115641a69281537adb477db665d0373b76851957c7015a20e85756b
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.127%
EPSS Percentile33rd percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 5 medium: 0 low: 0 git 2.49.1-r0 (apk)

pkg:apk/alpine/git@2.49.1-r0?os_name=alpine&os_version=3.22

high : CVE--2025--48385

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.102%
EPSS Percentile29th percentile
Description

high : CVE--2025--46334

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.021%
EPSS Percentile4th percentile
Description

high : CVE--2025--27614

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--46835

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.022%
EPSS Percentile4th percentile
Description

high : CVE--2025--48384

Affected range<2.50.1-r0
Fixed version2.50.1-r0
EPSS Score0.016%
EPSS Percentile2nd percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8-alpine

Name8.4-alpine3.22
Digestsha256:f5f0e78475a1280bb8f4a77fa426fbfc2390f418f51757359949cb8ebf79cc52
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed3 weeks ago
Size42 MB
Packages60
Flavoralpine
OS3.22
Runtime8.4
The base image is also available under the supported tag(s): 8-alpine3.22, 8-cli-alpine, 8-cli-alpine3.22, 8.4-alpine, 8.4-alpine3.22, 8.4-cli-alpine, 8.4-cli-alpine3.22, 8.4.10-cli-alpine, 8.4.10-cli-alpine3.22, alpine, alpine3.22, cli-alpine, cli-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
8.4.10-alpine
Minor runtime version update
Also known as:
  • 8.4.10-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.10
 3 weeks ago



@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.2-fpm-alpine

Name8.2.29-fpm-alpine3.22
Digestsha256:aaccb621d115641a69281537adb477db665d0373b76851957c7015a20e85756b
Vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
Pushed3 weeks ago
Size32 MB
Packages61
Flavoralpine
OS3.22
Runtime8.2.29
The base image is also available under the supported tag(s): 8.2-fpm-alpine3.22, 8.2.29-fpm-alpine, 8.2.29-fpm-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
8.3-fpm-alpine
Minor runtime version update
Also known as:
  • 8.3.23-fpm-alpine
  • 8.3.23-fpm-alpine3.22
  • 8.3-fpm-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 33 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.23
 3 weeks ago



8.4-fpm-alpine
Image has same number of vulnerabilities
Also known as:
  • 8.4.10-fpm-alpine
  • 8.4.10-fpm-alpine3.22
  • 8.4-fpm-alpine3.22
  • 8-fpm-alpine
  • 8-fpm-alpine3.22
  • fpm-alpine
  • fpm-alpine3.22
 Benefits:
  • Same OS detected
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
 3 weeks ago



@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.1-fpm-alpine

Name8.1.33-fpm-alpine3.21
Digestsha256:5871d3d4f16880e00a32bd2ed082d37eccc1e79473014df282c8d9207b940cb0
Vulnerabilitiescritical: 0 high: 1 medium: 0 low: 0
Pushed3 weeks ago
Size32 MB
Packages60
Flavoralpine
OS3.21
Runtime8.1.33
The base image is also available under the supported tag(s): 8.1-fpm-alpine3.21, 8.1.33-fpm-alpine, 8.1.33-fpm-alpine3.21

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
8.1-fpm-alpine3.22
Patch runtime version update
Also known as:
  • 8.1.33-fpm-alpine3.22
 Benefits:
  • Patch runtime version update
  • Same OS detected
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 32 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.1.33
 3 weeks ago



8.3-fpm-alpine
Minor runtime version update
Also known as:
  • 8.3.23-fpm-alpine
  • 8.3.23-fpm-alpine3.22
  • 8.3-fpm-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Tag was pushed more recently
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 33 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.23
 3 weeks ago



8.3-fpm-alpine3.21
Minor runtime version update
Also known as:
  • 8.3.23-fpm-alpine3.21
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 33 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.3.23
 3 weeks ago



8.2-fpm-alpine
Minor runtime version update
Also known as:
  • 8.2.29-fpm-alpine
  • 8.2.29-fpm-alpine3.22
  • 8.2-fpm-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
  • 8.2-fpm-alpine was pulled 4.1K times last month
Image details:
  • Size: 32 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.2.29
 3 weeks ago



8.2-fpm-alpine3.21
Minor runtime version update
Also known as:
  • 8.2.29-fpm-alpine3.21
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 32 MB
  • Flavor: alpine
  • OS: 3.21
  • Runtime: 8.2.29
 3 weeks ago



8.4-fpm-alpine
Image introduces no new vulnerability but removes 1
Also known as:
  • 8.4.10-fpm-alpine
  • 8.4.10-fpm-alpine3.22
  • 8.4-fpm-alpine3.22
  • 8-fpm-alpine
  • 8-fpm-alpine3.22
  • fpm-alpine
  • fpm-alpine3.22
 Benefits:
  • Same OS detected
  • Image has similar size
  • Image introduces no new vulnerability but removes 1
  • Image contains similar number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
 3 weeks ago



8.4-fpm-alpine3.21
Image has same number of vulnerabilities
Also known as:
  • 8.4.10-fpm-alpine3.21
  • 8-fpm-alpine3.21
  • fpm-alpine3.21
 Benefits:
  • Same OS detected
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.21
 3 weeks 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 c55543b to b37d348 Compare August 13, 2025 17:04
@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:4eb08de56aab69b6542794f68a42a017903ec7d46fdf915bc486c50f80dc2520
vulnerabilitiescritical: 1 high: 2 medium: 0 low: 0
platformlinux/amd64
size112 MB
packages249
📦 Base Image php:8.2-alpine
also known as
  • 8.2-alpine3.22
  • 8.2-cli-alpine
  • 8.2-cli-alpine3.22
  • 8.2.29-alpine
  • 8.2.29-alpine3.22
  • 8.2.29-cli-alpine
  • 8.2.29-cli-alpine3.22
  • d8f4974194fb8fae35528e5ff3f03ca3566ee2e502f953b7817e0cbefebf8a0d
digestsha256:cdee2ae021443a0806843448eb174a188d6e6d85377a2e5a9bcd44161001fb8d
vulnerabilitiescritical: 0 high: 0 medium: 0 low: 0
critical: 1 high: 1 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score38.497%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.188%
EPSS Percentile41st percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.3 (golang)

pkg:golang/stdlib@1.24.3

high : CVE--2025--22874

Affected range>=1.24.0-0
<1.24.4
Fixed version1.24.4
EPSS Score0.012%
EPSS Percentile1st percentile
Description

Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.

@github-actions
Copy link

github-actions bot commented Nov 25, 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

github-actions bot commented Nov 25, 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

github-actions bot commented Nov 25, 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 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
@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-25.x branch from 48f5f5d to fa726d5 Compare December 2, 2025 16:45
@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:a190280f2272eec7c7a4f90398eb6a8d4b88f0ecb375264b39cde81a6d15d939
vulnerabilitiescritical: 1 high: 5 medium: 0 low: 0
platformlinux/amd64
size112 MB
packages250
📦 Base Image php:8.4-fpm-alpine
also known as
  • 8.4-fpm-alpine3.22
  • 8.4.15-fpm-alpine
  • 8.4.15-fpm-alpine3.22
digestsha256:9af4cb7d0b7e71f238f9f6a8e540f58237050c7478cd6e135de986064f618142
vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
critical: 1 high: 2 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score42.906%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.217%
EPSS Percentile44th percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 2 medium: 0 low: 0 libpng 1.6.47-r0 (apk)

pkg:apk/alpine/libpng@1.6.47-r0?os_name=alpine&os_version=3.22

high : CVE--2025--65018

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.018%
EPSS Percentile4th percentile
Description

high : CVE--2025--64720

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.033%
EPSS Percentile9th percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.8 (golang)

pkg:golang/stdlib@1.24.8

high : CVE--2025--58187

Affected range<1.24.9
Fixed version1.24.9
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.

@github-actions
Copy link

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

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 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

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.4-fpm-alpine

Name8.4.15-fpm-alpine3.22
Digestsha256:9af4cb7d0b7e71f238f9f6a8e540f58237050c7478cd6e135de986064f618142
Vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
Pushed1 week ago
Size36 MB
Packages61
Flavoralpine
OS3.22
Runtime8.4.15
The base image is also available under the supported tag(s): 8.4-fpm-alpine3.22, 8.4.15-fpm-alpine, 8.4.15-fpm-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
8.5-fpm-alpine
Image has same number of vulnerabilities
Also known as:
  • 8.5.0-fpm-alpine
  • 8.5.0-fpm-alpine3.22
  • 8.5-fpm-alpine3.22
  • 8-fpm-alpine
  • 8-fpm-alpine3.22
  • fpm-alpine
  • fpm-alpine3.22
 Benefits:
  • Same OS detected
  • Image contains 1 fewer package
  • Image has similar size
  • Image has same number of vulnerabilities
Image details:
  • Size: 38 MB
  • Flavor: alpine
  • OS: 3.22
 1 week ago



@github-actions
Copy link

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

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:84955089d58e0edc56a6ce0ca9be5d54c97895075e2db3f44b8d427fe2748799
vulnerabilitiescritical: 1 high: 5 medium: 0 low: 0
platformlinux/amd64
size136 MB
packages284
📦 Base Image php:8.4-alpine
also known as
  • 8.4-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8.4.15-alpine
  • 8.4.15-alpine3.22
  • 8.4.15-cli-alpine
  • 8.4.15-cli-alpine3.22
digestsha256:13069fa0e1d5051c408265677497514a9ef952bff6caea7ed2fae4b79bac5b64
vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
critical: 1 high: 2 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score42.906%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.217%
EPSS Percentile44th percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 2 medium: 0 low: 0 libpng 1.6.47-r0 (apk)

pkg:apk/alpine/libpng@1.6.47-r0?os_name=alpine&os_version=3.22

high : CVE--2025--65018

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.018%
EPSS Percentile4th percentile
Description

high : CVE--2025--64720

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.033%
EPSS Percentile9th percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.8 (golang)

pkg:golang/stdlib@1.24.8

high : CVE--2025--58187

Affected range<1.24.9
Fixed version1.24.9
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.

@github-actions
Copy link

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



1 similar comment
@github-actions
Copy link

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

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:a604feff6a779e27a0b2bbd630ffa9990bf8784a0f5ac38bd482343e4324d1c8
vulnerabilitiescritical: 1 high: 5 medium: 0 low: 0
platformlinux/amd64
size109 MB
packages250
📦 Base Image php:8.3-fpm-alpine
also known as
  • 8.3-fpm-alpine3.22
  • 8.3.28-fpm-alpine
  • 8.3.28-fpm-alpine3.22
digestsha256:079d120f7788bf6670213591c3a55507fd6b67f75afe6ef903dc5c63380f7217
vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
critical: 1 high: 2 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score42.906%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.217%
EPSS Percentile44th percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 2 medium: 0 low: 0 libpng 1.6.47-r0 (apk)

pkg:apk/alpine/libpng@1.6.47-r0?os_name=alpine&os_version=3.22

high : CVE--2025--65018

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.018%
EPSS Percentile4th percentile
Description

high : CVE--2025--64720

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.033%
EPSS Percentile9th percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.8 (golang)

pkg:golang/stdlib@1.24.8

high : CVE--2025--58187

Affected range<1.24.9
Fixed version1.24.9
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.

@github-actions
Copy link

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

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:4b193ff6135d76e649a808cc177bfa033ec329cb89dde592b4a129112069d51b
vulnerabilitiescritical: 1 high: 5 medium: 0 low: 0
platformlinux/amd64
size118 MB
packages249
📦 Base Image php:8.4-alpine
also known as
  • 8.4-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8.4.15-alpine
  • 8.4.15-alpine3.22
  • 8.4.15-cli-alpine
  • 8.4.15-cli-alpine3.22
digestsha256:13069fa0e1d5051c408265677497514a9ef952bff6caea7ed2fae4b79bac5b64
vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
critical: 1 high: 2 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score42.906%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.217%
EPSS Percentile44th percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 2 medium: 0 low: 0 libpng 1.6.47-r0 (apk)

pkg:apk/alpine/libpng@1.6.47-r0?os_name=alpine&os_version=3.22

high : CVE--2025--65018

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.018%
EPSS Percentile4th percentile
Description

high : CVE--2025--64720

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.033%
EPSS Percentile9th percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.8 (golang)

pkg:golang/stdlib@1.24.8

high : CVE--2025--58187

Affected range<1.24.9
Fixed version1.24.9
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.

@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.4-alpine

Name8.4.15-alpine3.22
Digestsha256:13069fa0e1d5051c408265677497514a9ef952bff6caea7ed2fae4b79bac5b64
Vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
Pushed1 week ago
Size41 MB
Packages60
Flavoralpine
OS3.22
Runtime8.4.15
The base image is also available under the supported tag(s): 8.4-alpine3.22, 8.4-cli-alpine, 8.4-cli-alpine3.22, 8.4.15-alpine, 8.4.15-alpine3.22, 8.4.15-cli-alpine, 8.4.15-cli-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
8.5-alpine
Minor runtime version update
Also known as:
  • 8.5.0-cli-alpine
  • 8.5.0-cli-alpine3.22
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • cli-alpine
  • cli-alpine3.22
  • alpine
  • alpine3.22
  • 8.5.0-alpine3.22
  • 8.5-alpine3.22
  • 8-alpine
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image contains 1 fewer package
  • Image has similar size
  • Image has same number of vulnerabilities
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.5.0
 1 week ago



@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:5b7072b189f1a3a0e7eb29c15c3d0051f6189a8454d33af91175b0ca33459eab
vulnerabilitiescritical: 1 high: 5 medium: 0 low: 0
platformlinux/amd64
size114 MB
packages249
📦 Base Image php:8.3-alpine
also known as
  • 8.3-alpine3.22
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.22
  • 8.3.28-alpine
  • 8.3.28-alpine3.22
  • 8.3.28-cli-alpine
  • 8.3.28-cli-alpine3.22
digestsha256:d472137436dccea12eb4ebea28f394c1bf206260229ea6d7f4418d8f14c03174
vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
critical: 1 high: 2 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score42.906%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.217%
EPSS Percentile44th percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 2 medium: 0 low: 0 libpng 1.6.47-r0 (apk)

pkg:apk/alpine/libpng@1.6.47-r0?os_name=alpine&os_version=3.22

high : CVE--2025--65018

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.018%
EPSS Percentile4th percentile
Description

high : CVE--2025--64720

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.033%
EPSS Percentile9th percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.8 (golang)

pkg:golang/stdlib@1.24.8

high : CVE--2025--58187

Affected range<1.24.9
Fixed version1.24.9
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.

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:28e0d816af9f46a9beafe5d0709d8067562f4b8f3b4a4816373a67b8f735162b
vulnerabilitiescritical: 1 high: 5 medium: 0 low: 0
platformlinux/amd64
size133 MB
packages284
📦 Base Image php:8.3-alpine
also known as
  • 8.3-alpine3.22
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.22
  • 8.3.28-alpine
  • 8.3.28-alpine3.22
  • 8.3.28-cli-alpine
  • 8.3.28-cli-alpine3.22
digestsha256:d472137436dccea12eb4ebea28f394c1bf206260229ea6d7f4418d8f14c03174
vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
critical: 1 high: 2 medium: 0 low: 0 golang.org/x/crypto 0.17.0 (golang)

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

critical 9.1: CVE--2024--45337 Improper Authorization

Affected range<0.31.0
Fixed version0.31.0
CVSS Score9.1
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS Score42.906%
EPSS Percentile97th percentile
Description

Applications and libraries which misuse the ServerConfig.PublicKeyCallback callback may be susceptible to an authorization bypass.

The documentation for ServerConfig.PublicKeyCallback says that "A call to this function does not guarantee that the key offered is in fact used to authenticate." Specifically, the SSH protocol allows clients to inquire about whether a public key is acceptable before proving control of the corresponding private key. PublicKeyCallback may be called with multiple keys, and the order in which the keys were provided cannot be used to infer which key the client successfully authenticated with, if any. Some applications, which store the key(s) passed to PublicKeyCallback (or derived information) and make security relevant determinations based on it once the connection is established, may make incorrect assumptions.

For example, an attacker may send public keys A and B, and then authenticate with A. PublicKeyCallback would be called only twice, first with A and then with B. A vulnerable application may then make authorization decisions based on key B for which the attacker does not actually control the private key.

Since this API is widely misused, as a partial mitigation golang.org/x/crypto@v0.31.0 enforces the property that, when successfully authenticating via public key, the last key passed to ServerConfig.PublicKeyCallback will be the key used to authenticate the connection. PublicKeyCallback will now be called multiple times with the same key, if necessary. Note that the client may still not control the last key passed to PublicKeyCallback if the connection is then authenticated with a different method, such as PasswordCallback, KeyboardInteractiveCallback, or NoClientAuth.

Users should be using the Extensions field of the Permissions return value from the various authentication callbacks to record data associated with the authentication attempt instead of referencing external state. Once the connection is established the state corresponding to the successful authentication attempt can be retrieved via the ServerConn.Permissions field. Note that some third-party libraries misuse the Permissions type by sharing it across authentication attempts; users of third-party libraries should refer to the relevant projects for guidance.

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.

high : CVE--2025--22869

Affected range<0.35.0
Fixed version0.35.0
EPSS Score0.217%
EPSS Percentile44th percentile
Description

SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

critical: 0 high: 2 medium: 0 low: 0 libpng 1.6.47-r0 (apk)

pkg:apk/alpine/libpng@1.6.47-r0?os_name=alpine&os_version=3.22

high : CVE--2025--65018

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.018%
EPSS Percentile4th percentile
Description

high : CVE--2025--64720

Affected range<1.6.51-r0
Fixed version1.6.51-r0
EPSS Score0.033%
EPSS Percentile9th percentile
Description
critical: 0 high: 1 medium: 0 low: 0 stdlib 1.24.8 (golang)

pkg:golang/stdlib@1.24.8

high : CVE--2025--58187

Affected range<1.24.9
Fixed version1.24.9
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.

@github-actions
Copy link

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 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

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-fpm-alpine

Name8.3.28-fpm-alpine3.22
Digestsha256:079d120f7788bf6670213591c3a55507fd6b67f75afe6ef903dc5c63380f7217
Vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
Pushed1 week ago
Size33 MB
Packages61
Flavoralpine
OS3.22
Runtime8.3.28
The base image is also available under the supported tag(s): 8.3-fpm-alpine3.22, 8.3.28-fpm-alpine, 8.3.28-fpm-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
8.4-fpm-alpine
Minor runtime version update
Also known as:
  • 8.4.15-fpm-alpine
  • 8.4.15-fpm-alpine3.22
  • 8.4-fpm-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 36 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.15
 1 week ago



8.5-fpm-alpine
Image has same number of vulnerabilities
Also known as:
  • 8.5.0-fpm-alpine
  • 8.5.0-fpm-alpine3.22
  • 8.5-fpm-alpine3.22
  • 8-fpm-alpine
  • 8-fpm-alpine3.22
  • fpm-alpine
  • fpm-alpine3.22
 Benefits:
  • Same OS detected
  • Image contains 1 fewer package
  • Image has similar size
  • Image has same number of vulnerabilities
Image details:
  • Size: 38 MB
  • Flavor: alpine
  • OS: 3.22
 1 week ago



@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.4-alpine

Name8.4.15-alpine3.22
Digestsha256:13069fa0e1d5051c408265677497514a9ef952bff6caea7ed2fae4b79bac5b64
Vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
Pushed1 week ago
Size41 MB
Packages60
Flavoralpine
OS3.22
Runtime8.4.15
The base image is also available under the supported tag(s): 8.4-alpine3.22, 8.4-cli-alpine, 8.4-cli-alpine3.22, 8.4.15-alpine, 8.4.15-alpine3.22, 8.4.15-cli-alpine, 8.4.15-cli-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
8.5-alpine
Minor runtime version update
Also known as:
  • 8.5.0-cli-alpine
  • 8.5.0-cli-alpine3.22
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • cli-alpine
  • cli-alpine3.22
  • alpine
  • alpine3.22
  • 8.5.0-alpine3.22
  • 8.5-alpine3.22
  • 8-alpine
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image contains 1 fewer package
  • Image has similar size
  • Image has same number of vulnerabilities
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.5.0
 1 week ago



@github-actions
Copy link

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-alpine

Name8.3.28-alpine3.22
Digestsha256:d472137436dccea12eb4ebea28f394c1bf206260229ea6d7f4418d8f14c03174
Vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
Pushed1 week ago
Size37 MB
Packages60
Flavoralpine
OS3.22
Runtime8.3.28
The base image is also available under the supported tag(s): 8.3-alpine3.22, 8.3-cli-alpine, 8.3-cli-alpine3.22, 8.3.28-alpine, 8.3.28-alpine3.22, 8.3.28-cli-alpine, 8.3.28-cli-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
8.5-alpine
Minor runtime version update
Also known as:
  • 8.5.0-cli-alpine
  • 8.5.0-cli-alpine3.22
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • cli-alpine
  • cli-alpine3.22
  • alpine
  • alpine3.22
  • 8.5.0-alpine3.22
  • 8.5-alpine3.22
  • 8-alpine
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image contains 1 fewer package
  • Image has similar size
  • Image has same number of vulnerabilities
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.5.0
 1 week ago



8.4-alpine
Minor runtime version update
Also known as:
  • 8.4.15-cli-alpine
  • 8.4.15-cli-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8.4.15-alpine
  • 8.4.15-alpine3.22
  • 8.4-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 41 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.15
 1 week ago



@github-actions
Copy link

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

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

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-alpine

Name8.3.28-alpine3.22
Digestsha256:d472137436dccea12eb4ebea28f394c1bf206260229ea6d7f4418d8f14c03174
Vulnerabilitiescritical: 0 high: 0 medium: 2 low: 2
Pushed1 week ago
Size37 MB
Packages60
Flavoralpine
OS3.22
Runtime8.3.28
The base image is also available under the supported tag(s): 8.3-alpine3.22, 8.3-cli-alpine, 8.3-cli-alpine3.22, 8.3.28-alpine, 8.3.28-alpine3.22, 8.3.28-cli-alpine, 8.3.28-cli-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
8.5-alpine
Minor runtime version update
Also known as:
  • 8.5.0-cli-alpine
  • 8.5.0-cli-alpine3.22
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.22
  • 8-cli-alpine
  • 8-cli-alpine3.22
  • cli-alpine
  • cli-alpine3.22
  • alpine
  • alpine3.22
  • 8.5.0-alpine3.22
  • 8.5-alpine3.22
  • 8-alpine
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image contains 1 fewer package
  • Image has similar size
  • Image has same number of vulnerabilities
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.5.0
 1 week ago



8.4-alpine
Minor runtime version update
Also known as:
  • 8.4.15-cli-alpine
  • 8.4.15-cli-alpine3.22
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.22
  • 8.4.15-alpine
  • 8.4.15-alpine3.22
  • 8.4-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 41 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.4.15
 1 week ago



@github-actions
Copy link

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 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

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

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 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

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