Skip to content

deps(deps): update ansible/ansible-lint action to v26 #119

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 v26 #119

renovate wants to merge 1 commit into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2026

This PR contains the following updates:

Package Type Update Change
ansible/ansible-lint action major v25.6.1 → v26.1.0

Release Notes

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

v26.1.0

Compare Source

Fixes

Maintenance

v25.12.2

Compare Source

Fixes

Maintenance

v25.12.1

Compare Source

Features
Fixes
Maintenance

v25.12.0

Compare Source

Maintenance

v25.11.1

Compare Source

Features

Fixes

Maintenance

v25.11.0

Compare Source

Fixes

Maintenance

v25.9.2

Compare Source

Fixes

Maintenance

v25.9.1

Compare Source

Fixes

Maintenance

v25.9.0

Compare Source

Fixes

Maintenance

v25.8.2

Compare Source

Bugfixes

v25.8.1

Compare Source

Bugfixes

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

Maintenance

v25.8.0

Compare Source

Bugfixes

v25.7.0

Compare Source

Enhancements

Bugfixes

Maintenance

Configuration

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

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from lotyp as a code owner January 8, 2026 14:27
@renovate renovate bot enabled auto-merge (squash) January 8, 2026 14:27
@github-actions github-actions bot added the type: maintenance For maintenance, refactor and testing (perf, chore, style, revert, refactor, test, build, ci) label Jan 8, 2026
@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:7b24b3af63658103a0286285b9ece5180685cdfa74c02376f54fc37da86395be
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size109 MB
packages251
📦 Base Image php:8.3-fpm-alpine
also known as
  • 8.3-fpm-alpine3.23
  • 8.3.29-fpm-alpine
  • 8.3.29-fpm-alpine3.23
  • 84c6df40c76a0bcd532e70d2a1b4d0cecd45ad9655ba431d318ec37d612d7bf6
digestsha256:0a80c7265e776321e0e2010d7b0eb7bc54f0ea8f7584dd322ff15d0371926d4b
vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
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.025%
EPSS Percentile6th 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.215%
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: 1 medium: 0 low: 0 gnupg 2.4.8-r1 (apk)

pkg:apk/alpine/gnupg@2.4.8-r1?os_name=alpine&os_version=3.23

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-fpm-alpine

Name8.3.29-fpm-alpine3.23
Digestsha256:0a80c7265e776321e0e2010d7b0eb7bc54f0ea8f7584dd322ff15d0371926d4b
Vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
Pushed2 weeks ago
Size34 MB
Packages62
Flavoralpine
OS3.23
Runtime8.3.29
The base image is also available under the supported tag(s): 8.3-fpm-alpine3.23, 8.3.29-fpm-alpine, 8.3.29-fpm-alpine3.23

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.16-fpm-alpine
  • 8.4.16-fpm-alpine3.23
  • 8.4-fpm-alpine3.23
 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: 36 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.4.16
 2 weeks ago



8.5-fpm-alpine
Image has same number of vulnerabilities
Also known as:
  • 8.5.1-fpm-alpine
  • 8.5.1-fpm-alpine3.23
  • 8.5-fpm-alpine3.23
  • 8-fpm-alpine
  • 8-fpm-alpine3.23
  • fpm-alpine
  • fpm-alpine3.23
 Benefits:
  • Same OS detected
  • Image contains 1 fewer package
  • Tag was pushed more recently
  • Image has similar size
  • Image has same number of vulnerabilities
Image details:
  • Size: 38 MB
  • Flavor: alpine
  • OS: 3.23
 2 weeks ago



@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:fda69d5cfb02fd955ed084b259ffe880e8bf83b6bd0ee4f3b8d2d7cfd89e96b1
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size133 MB
packages285
📦 Base Image php:2d9d9d0610811d72bd332d556830f9ee027f885c1c04f540172288d3525aecc5
also known as
  • 8.3-alpine
  • 8.3-alpine3.23
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.23
  • 8.3.29-alpine
  • 8.3.29-cli-alpine3.23
digestsha256:55dd280d2f913218b52230b55c4779a3549200cec9b2993e0a91ee3ea4323994
vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
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.025%
EPSS Percentile6th 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.215%
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: 1 medium: 0 low: 0 gnupg 2.4.8-r1 (apk)

pkg:apk/alpine/gnupg@2.4.8-r1?os_name=alpine&os_version=3.23

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-alpine

Name8.3-alpine3.23
Digestsha256:55dd280d2f913218b52230b55c4779a3549200cec9b2993e0a91ee3ea4323994
Vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
Pushed2 weeks ago
Size38 MB
Packages61
Flavoralpine
OS3.23
Runtime8.3
The base image is also available under the supported tag(s): 8.3-alpine3.23, 8.3-cli-alpine, 8.3-cli-alpine3.23, 8.3.29-alpine, 8.3.29-cli-alpine3.23

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.1-cli-alpine
  • 8.5.1-cli-alpine3.23
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.23
  • 8-cli-alpine
  • 8-cli-alpine3.23
  • cli-alpine
  • cli-alpine3.23
  • alpine
  • alpine3.23
  • 8.5.1-alpine
  • 8.5.1-alpine3.23
  • 8.5-alpine3.23
  • 8-alpine
  • 8-alpine3.23
 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.23
  • Runtime: 8.5.1
 2 weeks ago



8.4-alpine
Minor runtime version update
Also known as:
  • 8.4.16-cli-alpine
  • 8.4.16-cli-alpine3.23
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.23
  • 8.4.16-alpine
  • 8.4.16-alpine3.23
  • 8.4-alpine3.23
 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: 41 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.4.16
 2 weeks ago



@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:8b8af003a155bb5b042f72e3f536122093826d3e1c22a4626a209b101d2ccf83
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size113 MB
packages250
📦 Base Image php:8.2-alpine
also known as
  • 8.2-alpine3.23
  • 8.2-cli-alpine
  • 8.2-cli-alpine3.23
  • 8.2.30-alpine
  • 8.2.30-alpine3.23
  • 8.2.30-cli-alpine
  • 8.2.30-cli-alpine3.23
digestsha256:dad4e0c31503684d830285906fc548ea6788310260a670a9cd579f69636d873c
vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
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.025%
EPSS Percentile6th 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.215%
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: 1 medium: 0 low: 0 gnupg 2.4.8-r1 (apk)

pkg:apk/alpine/gnupg@2.4.8-r1?os_name=alpine&os_version=3.23

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:4fcca0d03b3b783e3bcaddc7c2d41014c86e2bcaaa1b78946573e2d47ad15af4
vulnerabilitiescritical: 1 high: 8 medium: 0 low: 0
platformlinux/amd64
size105 MB
packages248
📦 Base Image php:3604fed52d81970a176cafe8300295cf4ba1d0b9d7ca9dfc060e2f2e64591f54
also known as
  • 8.1-fpm-alpine3.21
  • 8.1.34-fpm-alpine
  • 8.1.34-fpm-alpine3.21
digestsha256:e1c21e70e250ddeed10edb10f9476389d0eb9e2122aeca5d46d05fd97ad3c043
vulnerabilitiescritical: 1 high: 0 medium: 5 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.025%
EPSS Percentile6th 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.215%
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: 5 medium: 0 low: 0 stdlib 1.23.9 (golang)

pkg:golang/stdlib@1.23.9

high : CVE--2025--61729

Affected range<1.24.11
Fixed version1.24.11
EPSS Score0.015%
EPSS Percentile2nd percentile
Description

Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in excessive resource consumption.

high : CVE--2025--61725

Affected range<1.24.8
Fixed version1.24.8
EPSS Score0.031%
EPSS Percentile8th percentile
Description

The ParseAddress function constructs 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.24.8
Fixed version1.24.8
EPSS Score0.031%
EPSS Percentile8th 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.24.8
Fixed version1.24.8
EPSS Score0.016%
EPSS Percentile3rd 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.24.9
Fixed version1.24.9
EPSS Score0.016%
EPSS Percentile3rd 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 gnupg 2.4.7-r0 (apk)

pkg:apk/alpine/gnupg@2.4.7-r0?os_name=alpine&os_version=3.21

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:8cbf518fd59b2d4f5415bb1ed0874b93ccfe9bf82a5708f18afc0ccee4cbf0a0
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size112 MB
packages251
📦 Base Image php:8.4-fpm-alpine
also known as
  • 8.4-fpm-alpine3.23
  • 8.4.16-fpm-alpine
  • 8.4.16-fpm-alpine3.23
digestsha256:96c072939e5497bce30cb0682f7397af04df01d4fcf78ede1dd6bdd3394e240f
vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
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.025%
EPSS Percentile6th 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.215%
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: 1 medium: 0 low: 0 gnupg 2.4.8-r1 (apk)

pkg:apk/alpine/gnupg@2.4.8-r1?os_name=alpine&os_version=3.23

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:0e720182b9218710babb76555b82d909dcd41adc814ba740a0c3f677abd60c43
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size118 MB
packages250
📦 Base Image php:8.4-alpine
also known as
  • 8.4-alpine3.23
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.23
  • 8.4.16-alpine
  • 8.4.16-alpine3.23
  • 8.4.16-cli-alpine
  • 8.4.16-cli-alpine3.23
digestsha256:d07aff446f152e78003bdbf5f625f44501ba75bccfc6bfd6dc79ba3489a90db8
vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
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.025%
EPSS Percentile6th 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.215%
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: 1 medium: 0 low: 0 gnupg 2.4.8-r1 (apk)

pkg:apk/alpine/gnupg@2.4.8-r1?os_name=alpine&os_version=3.23

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:6ff00112eb682bf627bc92c79acec0f39e97dba984106e6101afebc19cc235ac
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size109 MB
packages251
📦 Base Image php:8.2-fpm-alpine
also known as
  • 8.2-fpm-alpine3.23
  • 8.2.30-fpm-alpine
  • 8.2.30-fpm-alpine3.23
digestsha256:ea3dec3a85d02c19f088dc4385934af92b28f6c0b2d7318c72b340cac487b821
vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
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.025%
EPSS Percentile6th 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.215%
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: 1 medium: 0 low: 0 gnupg 2.4.8-r1 (apk)

pkg:apk/alpine/gnupg@2.4.8-r1?os_name=alpine&os_version=3.23

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.2-alpine

Name8.2.30-alpine3.23
Digestsha256:dad4e0c31503684d830285906fc548ea6788310260a670a9cd579f69636d873c
Vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
Pushed2 weeks ago
Size37 MB
Packages61
Flavoralpine
OS3.23
Runtime8.2.30
The base image is also available under the supported tag(s): 8.2-alpine3.23, 8.2-cli-alpine, 8.2-cli-alpine3.23, 8.2.30-alpine, 8.2.30-alpine3.23, 8.2.30-cli-alpine, 8.2.30-cli-alpine3.23

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-alpine
Minor runtime version update
Also known as:
  • 8.4.16-cli-alpine
  • 8.4.16-cli-alpine3.23
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.23
  • 8.4.16-alpine
  • 8.4.16-alpine3.23
  • 8.4-alpine3.23
 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: 41 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.4.16
 2 weeks ago



8.3-alpine
Minor runtime version update
Also known as:
  • 8.3.29-cli-alpine3.23
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.23
  • 8.3.29-alpine
  • 8.3-alpine3.23
 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: 38 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.3
 2 weeks ago



8.5-alpine
Minor runtime version update
Also known as:
  • 8.5.1-cli-alpine
  • 8.5.1-cli-alpine3.23
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.23
  • 8-cli-alpine
  • 8-cli-alpine3.23
  • cli-alpine
  • cli-alpine3.23
  • alpine
  • alpine3.23
  • 8.5.1-alpine
  • 8.5.1-alpine3.23
  • 8.5-alpine3.23
  • 8-alpine
  • 8-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image contains 1 fewer package
  • Image has same number of vulnerabilities
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.5.1
 2 weeks ago



@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.4-fpm-alpine

Name8.4.16-fpm-alpine3.23
Digestsha256:96c072939e5497bce30cb0682f7397af04df01d4fcf78ede1dd6bdd3394e240f
Vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
Pushed2 weeks ago
Size36 MB
Packages62
Flavoralpine
OS3.23
Runtime8.4.16
The base image is also available under the supported tag(s): 8.4-fpm-alpine3.23, 8.4.16-fpm-alpine, 8.4.16-fpm-alpine3.23

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.1-fpm-alpine
  • 8.5.1-fpm-alpine3.23
  • 8.5-fpm-alpine3.23
  • 8-fpm-alpine
  • 8-fpm-alpine3.23
  • fpm-alpine
  • fpm-alpine3.23
 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.23
 2 weeks ago



@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:3604fed52d81970a176cafe8300295cf4ba1d0b9d7ca9dfc060e2f2e64591f54

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 Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:f5400eb7e63919a5e11d8e3332fddee499f65110f14d23a0c72728afe1911685
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size132 MB
packages285
📦 Base Image php:8.2-alpine
also known as
  • 8.2-alpine3.23
  • 8.2-cli-alpine
  • 8.2-cli-alpine3.23
  • 8.2.30-alpine
  • 8.2.30-alpine3.23
  • 8.2.30-cli-alpine
  • 8.2.30-cli-alpine3.23
digestsha256:dad4e0c31503684d830285906fc548ea6788310260a670a9cd579f69636d873c
vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
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.025%
EPSS Percentile6th 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.215%
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: 1 medium: 0 low: 0 gnupg 2.4.8-r1 (apk)

pkg:apk/alpine/gnupg@2.4.8-r1?os_name=alpine&os_version=3.23

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:816861c27a1e6457e9a21bf4ea32df95edd64af2b91a25977b052a80fbea30ac
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size137 MB
packages285
📦 Base Image php:8.4-alpine
also known as
  • 8.4-alpine3.23
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.23
  • 8.4.16-alpine
  • 8.4.16-alpine3.23
  • 8.4.16-cli-alpine
  • 8.4.16-cli-alpine3.23
digestsha256:d07aff446f152e78003bdbf5f625f44501ba75bccfc6bfd6dc79ba3489a90db8
vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
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.025%
EPSS Percentile6th 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.215%
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: 1 medium: 0 low: 0 gnupg 2.4.8-r1 (apk)

pkg:apk/alpine/gnupg@2.4.8-r1?os_name=alpine&os_version=3.23

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.2-fpm-alpine

Name8.2.30-fpm-alpine3.23
Digestsha256:ea3dec3a85d02c19f088dc4385934af92b28f6c0b2d7318c72b340cac487b821
Vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
Pushed2 weeks ago
Size33 MB
Packages62
Flavoralpine
OS3.23
Runtime8.2.30
The base image is also available under the supported tag(s): 8.2-fpm-alpine3.23, 8.2.30-fpm-alpine, 8.2.30-fpm-alpine3.23

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.16-fpm-alpine
  • 8.4.16-fpm-alpine3.23
  • 8.4-fpm-alpine3.23
 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: 36 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.4.16
 2 weeks ago



8.3-fpm-alpine
Minor runtime version update
Also known as:
  • 8.3.29-fpm-alpine
  • 8.3.29-fpm-alpine3.23
  • 8.3-fpm-alpine3.23
 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: 34 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.3.29
 2 weeks ago



8.5-fpm-alpine
Image has same number of vulnerabilities
Also known as:
  • 8.5.1-fpm-alpine
  • 8.5.1-fpm-alpine3.23
  • 8.5-fpm-alpine3.23
  • 8-fpm-alpine
  • 8-fpm-alpine3.23
  • fpm-alpine
  • fpm-alpine3.23
 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.23
 2 weeks ago



@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.4-alpine

Name8.4.16-alpine3.23
Digestsha256:d07aff446f152e78003bdbf5f625f44501ba75bccfc6bfd6dc79ba3489a90db8
Vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
Pushed2 weeks ago
Size41 MB
Packages61
Flavoralpine
OS3.23
Runtime8.4.16
The base image is also available under the supported tag(s): 8.4-alpine3.23, 8.4-cli-alpine, 8.4-cli-alpine3.23, 8.4.16-alpine, 8.4.16-alpine3.23, 8.4.16-cli-alpine, 8.4.16-cli-alpine3.23

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.1-cli-alpine
  • 8.5.1-cli-alpine3.23
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.23
  • 8-cli-alpine
  • 8-cli-alpine3.23
  • cli-alpine
  • cli-alpine3.23
  • alpine
  • alpine3.23
  • 8.5.1-alpine
  • 8.5.1-alpine3.23
  • 8.5-alpine3.23
  • 8-alpine
  • 8-alpine3.23
 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.23
  • Runtime: 8.5.1
 2 weeks ago



1 similar comment
@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.4-alpine

Name8.4.16-alpine3.23
Digestsha256:d07aff446f152e78003bdbf5f625f44501ba75bccfc6bfd6dc79ba3489a90db8
Vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
Pushed2 weeks ago
Size41 MB
Packages61
Flavoralpine
OS3.23
Runtime8.4.16
The base image is also available under the supported tag(s): 8.4-alpine3.23, 8.4-cli-alpine, 8.4-cli-alpine3.23, 8.4.16-alpine, 8.4.16-alpine3.23, 8.4.16-cli-alpine, 8.4.16-cli-alpine3.23

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.1-cli-alpine
  • 8.5.1-cli-alpine3.23
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.23
  • 8-cli-alpine
  • 8-cli-alpine3.23
  • cli-alpine
  • cli-alpine3.23
  • alpine
  • alpine3.23
  • 8.5.1-alpine
  • 8.5.1-alpine3.23
  • 8.5-alpine3.23
  • 8-alpine
  • 8-alpine3.23
 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.23
  • Runtime: 8.5.1
 2 weeks ago



@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.2-alpine

Name8.2.30-alpine3.23
Digestsha256:dad4e0c31503684d830285906fc548ea6788310260a670a9cd579f69636d873c
Vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
Pushed2 weeks ago
Size37 MB
Packages61
Flavoralpine
OS3.23
Runtime8.2.30
The base image is also available under the supported tag(s): 8.2-alpine3.23, 8.2-cli-alpine, 8.2-cli-alpine3.23, 8.2.30-alpine, 8.2.30-alpine3.23, 8.2.30-cli-alpine, 8.2.30-cli-alpine3.23

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-alpine
Minor runtime version update
Also known as:
  • 8.4.16-cli-alpine
  • 8.4.16-cli-alpine3.23
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.23
  • 8.4.16-alpine
  • 8.4.16-alpine3.23
  • 8.4-alpine3.23
 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: 41 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.4.16
 2 weeks ago



8.3-alpine
Minor runtime version update
Also known as:
  • 8.3.29-cli-alpine3.23
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.23
  • 8.3.29-alpine
  • 8.3-alpine3.23
 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: 38 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.3
 2 weeks ago



8.5-alpine
Minor runtime version update
Also known as:
  • 8.5.1-cli-alpine
  • 8.5.1-cli-alpine3.23
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.23
  • 8-cli-alpine
  • 8-cli-alpine3.23
  • cli-alpine
  • cli-alpine3.23
  • alpine
  • alpine3.23
  • 8.5.1-alpine
  • 8.5.1-alpine3.23
  • 8.5-alpine3.23
  • 8-alpine
  • 8-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image contains 1 fewer package
  • Image has same number of vulnerabilities
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.5.1
 2 weeks ago



@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:a1bd093974b60fb256cd59ad8bf57b8cb42da0044bdcc14d2bc2143bf0e67cf5
vulnerabilitiescritical: 1 high: 3 medium: 0 low: 0
platformlinux/amd64
size114 MB
packages250
📦 Base Image php:2d9d9d0610811d72bd332d556830f9ee027f885c1c04f540172288d3525aecc5
also known as
  • 8.3-alpine
  • 8.3-alpine3.23
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.23
  • 8.3.29-alpine
  • 8.3.29-cli-alpine3.23
digestsha256:55dd280d2f913218b52230b55c4779a3549200cec9b2993e0a91ee3ea4323994
vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
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.025%
EPSS Percentile6th 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.215%
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: 1 medium: 0 low: 0 gnupg 2.4.8-r1 (apk)

pkg:apk/alpine/gnupg@2.4.8-r1?os_name=alpine&os_version=3.23

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.3-alpine

Name8.3-alpine3.23
Digestsha256:55dd280d2f913218b52230b55c4779a3549200cec9b2993e0a91ee3ea4323994
Vulnerabilitiescritical: 1 high: 0 medium: 4 low: 0 unspecified: 3
Pushed2 weeks ago
Size38 MB
Packages61
Flavoralpine
OS3.23
Runtime8.3
The base image is also available under the supported tag(s): 8.3-alpine3.23, 8.3-cli-alpine, 8.3-cli-alpine3.23, 8.3.29-alpine, 8.3.29-cli-alpine3.23

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.1-cli-alpine
  • 8.5.1-cli-alpine3.23
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.23
  • 8-cli-alpine
  • 8-cli-alpine3.23
  • cli-alpine
  • cli-alpine3.23
  • alpine
  • alpine3.23
  • 8.5.1-alpine
  • 8.5.1-alpine3.23
  • 8.5-alpine3.23
  • 8-alpine
  • 8-alpine3.23
 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.23
  • Runtime: 8.5.1
 2 weeks ago



8.4-alpine
Minor runtime version update
Also known as:
  • 8.4.16-cli-alpine
  • 8.4.16-cli-alpine3.23
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.23
  • 8.4.16-alpine
  • 8.4.16-alpine3.23
  • 8.4-alpine3.23
 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: 41 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.4.16
 2 weeks ago



@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:d9e81b69e7372f42578ea1fcc0d551f5ceccba2bb86c986817e752c3bb45a57e
vulnerabilitiescritical: 1 high: 9 medium: 0 low: 0
platformlinux/amd64
size128 MB
packages265
📦 Base Image php:8.1-alpine
also known as
  • 8.1-alpine3.21
  • 8.1-cli-alpine
  • 8.1-cli-alpine3.21
  • 8.1.34-alpine
  • 8.1.34-alpine3.21
  • 8.1.34-cli-alpine3.21
  • d0b581c71ccd5071323b105fbcf784f0cc839918e8992e56fe275df9dc840f2b
digestsha256:5a3201a62206d5168ce3bc9fe81cf35c07c93b4c213cff448ecbf5686161271a
vulnerabilitiescritical: 1 high: 0 medium: 5 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.025%
EPSS Percentile6th 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.215%
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: 5 medium: 0 low: 0 stdlib 1.23.9 (golang)

pkg:golang/stdlib@1.23.9

high : CVE--2025--61729

Affected range<1.24.11
Fixed version1.24.11
EPSS Score0.015%
EPSS Percentile2nd percentile
Description

Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in excessive resource consumption.

high : CVE--2025--61725

Affected range<1.24.8
Fixed version1.24.8
EPSS Score0.031%
EPSS Percentile8th percentile
Description

The ParseAddress function constructs 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.24.8
Fixed version1.24.8
EPSS Score0.031%
EPSS Percentile8th 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.24.8
Fixed version1.24.8
EPSS Score0.016%
EPSS Percentile3rd 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.24.9
Fixed version1.24.9
EPSS Score0.016%
EPSS Percentile3rd 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 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.135%
EPSS Percentile34th 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 gnupg 2.4.7-r0 (apk)

pkg:apk/alpine/gnupg@2.4.7-r0?os_name=alpine&os_version=3.21

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026 •
edited
Loading

Outdated

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.1-alpine

Name8.1.34-alpine3.21
Digestsha256:5a3201a62206d5168ce3bc9fe81cf35c07c93b4c213cff448ecbf5686161271a
Vulnerabilitiescritical: 1 high: 0 medium: 5 low: 2
Pushed2 weeks ago
Size36 MB
Packages59
Flavoralpine
OS3.21
Runtime8.1.34

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-alpine
Minor runtime version update
Also known as:
  • 8.4.16-cli-alpine
  • 8.4.16-cli-alpine3.23
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.23
  • 8.4.16-alpine
  • 8.4.16-alpine3.23
  • 8.4-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 3
  • Image contains similar number of packages
Image details:
  • Size: 41 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.4.16
 2 weeks ago



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



8.3-alpine3.22
Minor runtime version update
Also known as:
  • 8.3.29-cli-alpine3.22
  • 8.3-cli-alpine3.22
  • 8.3.29-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains similar number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.29
 2 weeks ago



8.3-alpine
Minor runtime version update
Also known as:
  • 8.3.29-cli-alpine3.23
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.23
  • 8.3.29-alpine
  • 8.3-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 3
  • Image contains similar number of packages
Image details:
  • Size: 38 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.3
 2 weeks ago



8.2-alpine
Minor runtime version update
Also known as:
  • 8.2.30-cli-alpine
  • 8.2.30-cli-alpine3.23
  • 8.2-cli-alpine
  • 8.2-cli-alpine3.23
  • 8.2.30-alpine
  • 8.2.30-alpine3.23
  • 8.2-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 3
  • 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.23
  • Runtime: 8.2.30
 2 weeks ago



8.2-alpine3.22
Minor runtime version update
Also known as:
  • 8.2.30-cli-alpine3.22
  • 8.2-cli-alpine3.22
  • 8.2.30-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains similar number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.2.30
 2 weeks ago



8.5-alpine
Minor runtime version update
Also known as:
  • 8.5.1-cli-alpine
  • 8.5.1-cli-alpine3.23
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.23
  • 8-cli-alpine
  • 8-cli-alpine3.23
  • cli-alpine
  • cli-alpine3.23
  • alpine
  • alpine3.23
  • 8.5.1-alpine
  • 8.5.1-alpine3.23
  • 8.5-alpine3.23
  • 8-alpine
  • 8-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image introduces no new vulnerability but removes 3
  • Image contains similar number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.5.1
 2 weeks ago



8.5-alpine3.22
Minor runtime version update
Also known as:
  • 8.5.1-cli-alpine3.22
  • 8.5-cli-alpine3.22
  • 8-cli-alpine3.22
  • cli-alpine3.22
  • alpine3.22
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.5
 2 weeks ago



@github-actions
Copy link

github-actions bot commented Jan 8, 2026

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:439cf8238d695eea8df5cdc9853ef5f2ad381d396670e1b47ac9a9470b988bb0
vulnerabilitiescritical: 1 high: 8 medium: 0 low: 0
platformlinux/amd64
size109 MB
packages247
📦 Base Image php:8.1-alpine
also known as
  • 8.1-alpine3.21
  • 8.1-cli-alpine
  • 8.1-cli-alpine3.21
  • 8.1.34-alpine
  • 8.1.34-alpine3.21
  • 8.1.34-cli-alpine3.21
  • d0b581c71ccd5071323b105fbcf784f0cc839918e8992e56fe275df9dc840f2b
digestsha256:5a3201a62206d5168ce3bc9fe81cf35c07c93b4c213cff448ecbf5686161271a
vulnerabilitiescritical: 1 high: 0 medium: 5 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.025%
EPSS Percentile6th 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.215%
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: 5 medium: 0 low: 0 stdlib 1.23.9 (golang)

pkg:golang/stdlib@1.23.9

high : CVE--2025--61729

Affected range<1.24.11
Fixed version1.24.11
EPSS Score0.015%
EPSS Percentile2nd percentile
Description

Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in excessive resource consumption.

high : CVE--2025--61725

Affected range<1.24.8
Fixed version1.24.8
EPSS Score0.031%
EPSS Percentile8th percentile
Description

The ParseAddress function constructs 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.24.8
Fixed version1.24.8
EPSS Score0.031%
EPSS Percentile8th 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.24.8
Fixed version1.24.8
EPSS Score0.016%
EPSS Percentile3rd 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.24.9
Fixed version1.24.9
EPSS Score0.016%
EPSS Percentile3rd 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 gnupg 2.4.7-r0 (apk)

pkg:apk/alpine/gnupg@2.4.7-r0?os_name=alpine&os_version=3.21

high : CVE--2025--68973

Affected range<2.4.9-r0
Fixed version2.4.9-r0
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

@github-actions
Copy link

github-actions bot commented Jan 8, 2026

Recommended fixes for image wayofdev/php-dev:latest

Base image is php:8.1-alpine

Name8.1.34-alpine3.21
Digestsha256:5a3201a62206d5168ce3bc9fe81cf35c07c93b4c213cff448ecbf5686161271a
Vulnerabilitiescritical: 1 high: 0 medium: 5 low: 2
Pushed2 weeks ago
Size36 MB
Packages59
Flavoralpine
OS3.21
Runtime8.1.34

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-alpine
Minor runtime version update
Also known as:
  • 8.4.16-cli-alpine
  • 8.4.16-cli-alpine3.23
  • 8.4-cli-alpine
  • 8.4-cli-alpine3.23
  • 8.4.16-alpine
  • 8.4.16-alpine3.23
  • 8.4-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 3
  • Image contains similar number of packages
Image details:
  • Size: 41 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.4.16
 2 weeks ago



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



8.3-alpine3.22
Minor runtime version update
Also known as:
  • 8.3.29-cli-alpine3.22
  • 8.3-cli-alpine3.22
  • 8.3.29-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains similar number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.3.29
 2 weeks ago



8.3-alpine
Minor runtime version update
Also known as:
  • 8.3.29-cli-alpine3.23
  • 8.3-cli-alpine
  • 8.3-cli-alpine3.23
  • 8.3.29-alpine
  • 8.3-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 3
  • Image contains similar number of packages
Image details:
  • Size: 38 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.3
 2 weeks ago



8.2-alpine
Minor runtime version update
Also known as:
  • 8.2.30-cli-alpine
  • 8.2.30-cli-alpine3.23
  • 8.2-cli-alpine
  • 8.2-cli-alpine3.23
  • 8.2.30-alpine
  • 8.2.30-alpine3.23
  • 8.2-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image introduces no new vulnerability but removes 3
  • 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.23
  • Runtime: 8.2.30
 2 weeks ago



8.2-alpine3.22
Minor runtime version update
Also known as:
  • 8.2.30-cli-alpine3.22
  • 8.2-cli-alpine3.22
  • 8.2.30-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has similar size
  • Image has same number of vulnerabilities
  • Image contains similar number of packages
Image details:
  • Size: 37 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.2.30
 2 weeks ago



8.5-alpine
Minor runtime version update
Also known as:
  • 8.5.1-cli-alpine
  • 8.5.1-cli-alpine3.23
  • 8.5-cli-alpine
  • 8.5-cli-alpine3.23
  • 8-cli-alpine
  • 8-cli-alpine3.23
  • cli-alpine
  • cli-alpine3.23
  • alpine
  • alpine3.23
  • 8.5.1-alpine
  • 8.5.1-alpine3.23
  • 8.5-alpine3.23
  • 8-alpine
  • 8-alpine3.23
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image introduces no new vulnerability but removes 3
  • Image contains similar number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.23
  • Runtime: 8.5.1
 2 weeks ago



8.5-alpine3.22
Minor runtime version update
Also known as:
  • 8.5.1-cli-alpine3.22
  • 8.5-cli-alpine3.22
  • 8-cli-alpine3.22
  • cli-alpine3.22
  • alpine3.22
  • 8-alpine3.22
 Benefits:
  • Same OS detected
  • Minor runtime version update
  • Image has same number of vulnerabilities
  • Image contains equal number of packages
Image details:
  • Size: 44 MB
  • Flavor: alpine
  • OS: 3.22
  • Runtime: 8.5
 2 weeks 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