fix(deps): update backend dependencies#784
Open
renovate-sh-app[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate-sh-app
Bot
force-pushed
the
renovate/backend-dependencies
branch
10 times, most recently
from
July 22, 2026 10:02
a16cb13 to
1534c32
Compare
| datasource | package | from | to | | ---------- | ---------------------------------------------------------------------------- | ---------------------------------- | ---------------------------------- | | go | github.com/apache/arrow-go/v18 | v18.5.2 | v18.7.0 | | go | github.com/bradleyfalzon/ghinstallation/v2 | v2.18.0 | v2.19.0 | | go | github.com/clipperhouse/displaywidth | v0.10.0 | v0.11.0 | | go | github.com/clipperhouse/uax29/v2 | v2.6.0 | v2.7.0 | | go | github.com/emicklei/go-restful/v3 | v3.11.0 | v3.13.0 | | go | github.com/fatih/color | v1.18.0 | v1.19.0 | | go | github.com/go-openapi/jsonpointer | v0.22.5 | v0.24.0 | | go | github.com/go-openapi/jsonreference | v0.21.5 | v0.21.6 | | go | github.com/go-openapi/swag | v0.23.0 | v0.27.1 | | go | github.com/go-openapi/swag/jsonname | v0.25.5 | v0.27.1 | | go | github.com/goccy/go-json | v0.10.5 | v0.10.6 | | go | github.com/google/gnostic-models | v0.7.0 | v0.7.1 | | go | github.com/grafana/grafana-plugin-sdk-go | v0.291.1 | v0.293.0 | | go | github.com/grafana/otel-profiling-go | v0.5.1 | v0.6.0 | | go | github.com/grafana/pyroscope-go/godeltaprof | v0.1.9 | v0.1.12 | | go | github.com/grafana/schemads | v0.0.8 | v0.2.3 | | go | github.com/grpc-ecosystem/grpc-gateway/v2 | v2.28.0 | v2.29.0 | | go | github.com/hashicorp/go-plugin | v1.7.0 | v1.8.0 | | go | github.com/huandu/go-sqlbuilder | v1.39.1 | v1.42.1 | | go | github.com/huandu/xstrings | v1.4.0 | v1.5.0 | | go | github.com/jaegertracing/jaeger-idl | v0.6.0 | v0.9.0 | | go | github.com/klauspost/compress | v1.18.4 | v1.19.0 | | go | github.com/klauspost/cpuid/v2 | v2.3.0 | v2.4.0 | | go | github.com/magefile/mage | v1.16.1 | v1.17.2 | | go | github.com/mailru/easyjson | v0.7.7 | v0.9.2 | | go | github.com/mattn/go-colorable | v0.1.14 | v0.1.15 | | go | github.com/mattn/go-isatty | v0.0.20 | v0.0.23 | | go | github.com/mattn/go-runewidth | v0.0.19 | v0.0.24 | | go | github.com/oklog/run | v1.1.0 | v1.2.0 | | go | github.com/olekukonko/errors | v1.2.0 | v1.3.0 | | go | github.com/olekukonko/ll | v0.1.6 | v0.1.8 | | go | github.com/pierrec/lz4/v4 | v4.1.25 | v4.1.27 | | go | github.com/prometheus/common | v0.67.5 | v0.70.0 | | go | github.com/prometheus/procfs | v0.16.1 | v0.21.1 | | go | github.com/shurcooL/graphql | v0.0.0-20220606043923-3cf50f8a0a29 | v0.0.0-20240915155400-7ee5256398cf | | go | go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc | v0.67.0 | v0.69.0 | | go | go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace | v0.67.0 | v0.69.0 | | go | go.opentelemetry.io/contrib/propagators/jaeger | v1.42.0 | v1.44.0 | | go | go.opentelemetry.io/contrib/samplers/jaegerremote | v0.36.0 | v0.37.1 | | go | go.opentelemetry.io/otel | v1.43.0 | v1.44.0 | | go | go.opentelemetry.io/otel/exporters/otlp/otlptrace | v1.42.0 | v1.44.0 | | go | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc | v1.42.0 | v1.44.0 | | go | go.opentelemetry.io/otel/metric | v1.43.0 | v1.44.0 | | go | go.opentelemetry.io/otel/sdk | v1.43.0 | v1.44.0 | | go | go.opentelemetry.io/otel/trace | v1.43.0 | v1.44.0 | | go | go.opentelemetry.io/proto/otlp | v1.9.0 | v1.10.0 | | go | go.yaml.in/yaml/v2 | v2.4.3 | v2.4.4 | | go | golang.org/x/exp | v0.0.0-20260112195511-716be5621a96 | v0.0.0-20260718201538-764159d718ef | | go | golang.org/x/mod | v0.34.0 | v0.38.0 | | go | golang.org/x/net | v0.53.0 | v0.56.0 | | go | golang.org/x/sync | v0.20.0 | v0.22.0 | | go | golang.org/x/sys | v0.43.0 | v0.44.0 | | go | golang.org/x/telemetry | v0.0.0-20260311193753-579e4da9a98c | v0.0.0-20260717140457-bdb89881bb75 | | go | golang.org/x/text | v0.36.0 | v0.39.0 | | go | golang.org/x/tools | v0.43.0 | v0.48.0 | | go | google.golang.org/grpc | v1.79.3 | v1.82.1 | | go | pgregory.net/rapid | v1.2.0 | v1.3.0 | Signed-off-by: renovate-sh-app[bot] <219655108+renovate-sh-app[bot]@users.noreply.github.com>
renovate-sh-app
Bot
force-pushed
the
renovate/backend-dependencies
branch
from
July 22, 2026 22:03
1534c32 to
9ece495
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v18.5.2→v18.7.0v2.18.0→v2.19.0v0.10.0→v0.11.0v2.6.0→v2.7.0v3.11.0→v3.13.0v1.18.0→v1.19.0v0.22.5→v0.24.0v0.21.5→v0.21.6v0.23.0→v0.27.1v0.27.3(+1)v0.25.5→v0.27.1v0.27.3(+1)v0.10.5→v0.10.6v0.7.0→v0.7.1v0.291.1→v0.293.0v0.294.0v0.5.1→v0.6.0v0.1.9→v0.1.12v0.0.8→v0.2.3v2.28.0→v2.29.0v1.7.0→v1.8.0v1.39.1→v1.42.1v1.4.0→v1.5.0v0.6.0→v0.9.0640a500→7f666eev1.18.4→v1.19.0v1.19.1v2.3.0→v2.4.0v1.16.1→v1.17.2v0.7.7→v0.9.2v0.1.14→v0.1.15v0.0.20→v0.0.23v0.0.19→v0.0.24v1.1.0→v1.2.0v1.2.0→v1.3.0v0.1.6→v0.1.8v4.1.25→v4.1.27v0.67.5→v0.70.0v0.70.1v0.16.1→v0.21.13cf50f8→7ee5256v0.67.0→v0.69.0v0.67.0→v0.69.0v1.42.0→v1.44.0v0.36.0→v0.37.1v1.43.0→v1.44.0v1.42.0→v1.44.0v1.42.0→v1.44.0v1.43.0→v1.44.0v1.43.0→v1.44.0v1.43.0→v1.44.0v1.9.0→v1.10.0v1.11.0v2.4.3→v2.4.4716be56→764159dv0.34.0→v0.38.0v0.53.0→v0.56.0v0.20.0→v0.22.0v0.43.0→v0.44.0579e4da→bdb8988v0.36.0→v0.39.0v0.43.0→v0.48.0v1.79.3→v1.82.1v1.2.0→v1.3.0Go Net HTML parser is vulnerable to denial of service
CVE-2026-25680 / GHSA-5cv4-jp36-h3mw
More information
Details
In Go Net (
golang.org/x/net) before verion 0.55.0, parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Go Net HTML parser is vulnerable to denial of service
CVE-2026-25680 / GHSA-5cv4-jp36-h3mw / GO-2026-5028
More information
Details
In Go Net (
golang.org/x/net) before verion 0.55.0, parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service.Severity
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Invoking incorrect handling of namespaced elements in foreign content in golang.org/x/net/html
CVE-2026-42506 / GO-2026-5025
More information
Details
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Invoking failure to reject ASCII-only Punycode-encoded labels in golang.org/x/net/idna
CVE-2026-39821 / GO-2026-5026
More information
Details
The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error.
This behavior can lead to privilege escalation in programs using the idna package. For example, a program which performs privilege checks on the ASCII hostname may reject "example.com" but permit "xn--example-.com". If that program subsequently converts the ASCII hostname to Unicode, it will inadvertently permits access to the Unicode name "example.com".
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Invoking incorrect handling of HTML elements in foreign content in golang.org/x/net/html
CVE-2026-42502 / GO-2026-5027
More information
Details
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Invoking denial of service when parsing arbitrary HTML in golang.org/x/net/html
CVE-2026-25680 / GHSA-5cv4-jp36-h3mw / GO-2026-5028
More information
Details
Parsing arbitrary HTML can consume excessive CPU time, possibly leading to denial of service.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Invoking incorrect handling of character references in DOCTYPE nodes in golang.org/x/net/html
CVE-2026-25681 / GO-2026-5029
More information
Details
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Invoking duplicate attributes can cause XSS in golang.org/x/net/html
CVE-2026-27136 / GO-2026-5030
More information
Details
Parsing arbitrary HTML which is then rendered using Render can result in an unexpected HTML tree. This can be leveraged to execute XSS attacks in applications that attempt to sanitize input HTML before rendering.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Parsing an invalid SVCB or HTTPS RR can panic in golang.org/x/net/dns/dnsmessage
CVE-2026-46600 / GO-2026-5942
More information
Details
Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Invoking integer overflow in NewNTUnicodeString in golang.org/x/sys/windows
CVE-2026-39824 / GO-2026-5024
More information
Details
NewNTUnicodeString does not check for string length overflow. When provided with a string that overflows the maximum size of a NTUnicodeString (a 16-bit number of bytes), it returns a truncated string rather than an error.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Infinite loop on invalid input in golang.org/x/text
CVE-2026-56852 / GO-2026-5970
More information
Details
A norm.Iter can enter an infinite loop when handling input containing invalid UTF-8 bytes.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
gRPC-Go: xDS RBAC and HTTP/2 Vulnerabilities
GHSA-hrxh-6v49-42gf
More information
Details
Multiple security vulnerabilities have been identified and addressed in grpc-go affecting the xDS RBAC authorization engine (internal/xds/rbac) and the HTTP/2 transport server implementation (internal/transport). These vulnerabilities could result in:
MetadataorRequestedServerNamefields.NOTrules around unsupported fields.Impact
What kind of vulnerability is it? Who is impacted?
xDS RBAC Authorization Bypass via
Metadata&RequestedServerNamematcherspermissionandprincipalrules (specificallyMetadataandRequestedServerName) were silently ignored and treated as no-ops.NOTrules (Permission_NotRule/Principal_NotId) or multi-conditionOR/ANDrules, silently dropping them changed the boolean logic flow of the authorization engine.As a result, policy evaluation decisions could fail open, allowing unauthorized clients to access protected gRPC services or resources.
HTTP/2 Rapid Reset Mitigation Bypass / Denial of Service via Stream Aborts
SETTINGSACKs or server-initiatedRST_STREAMs.When a client initiated a rapid flood of stream creation (
HEADERS) immediately followed by stream terminationRST_STREAM, items queued up in the control buffer without counting against the transport response frame threshold. An attacker can repeatedly trigger this flood sequence to bypass reader blocking, resulting in high CPU usage, and Denial of Service (DoS).Denial of Service (Panic) in xDS RBAC Engine via Unsupported Fields inside NOT Rules
NOTrule wrapped an unsupported or unhandled field (such asSourcedMetadata), the recursive step returned an empty matcher. This could result in a runtime panic when the RBAC engine attempts to authorize an incoming request.An attacker or misconfigured/malicious xDS management server delivering an LDS/RDS update containing a
NOTrule around an unhandled field causes the gRPC server process to crash immediately (CWE-248 / Denial of Service).Patches
Has the problem been patched? What versions should users upgrade to?
All three issues have been fixed in
masterand will be released in 1.82.1 shortly.Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
If upgrading grpc-go immediately is not possible, apply the following workarounds based on your deployment architecture:
Metadata,RequestedServerName, orNOTrules wrapping unsupported fields (such asSourcedMetadata) to grpc-go servers.max_concurrent_streamslimits and active rate limiting onRST_STREAMfrequency per connection.Severity
8.27.55.9Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
gRPC-Go: xDS RBAC and HTTP/2 Vulnerabilities
GHSA-hrxh-6v49-42gf
More information
Details
Multiple security vulnerabilities have been identified and addressed in grpc-go affecting the xDS RBAC authorization engine (internal/xds/rbac) and the HTTP/2 transport server implementation (internal/transport). These vulnerabilities could result in:
MetadataorRequestedServerNamefields.NOTrules around unsupported fields.Impact
What kind of vulnerability is it? Who is impacted?
xDS RBAC Authorization Bypass via
Metadata&RequestedServerNamematcherspermissionandprincipalrules (specificallyMetadataandRequestedServerName) were silently ignored and treated as no-ops.NOTrules (Permission_NotRule/Principal_NotId) or multi-conditionOR/ANDrules, silently dropping them changed the boolean logic flow of the authorization engine.As a result, policy evaluation decisions could fail open, allowing unauthorized clients to access protected gRPC services or resources.
HTTP/2 Rapid Reset Mitigation Bypass / Denial of Service via Stream Aborts
SETTINGSACKs or server-initiatedRST_STREAMs.When a client initiated a rapid flood of stream creation (
HEADERS) immediately followed by stream terminationRST_STREAM, items queued up in the control buffer without counting against the transport response frame threshold. An attacker can repeatedly trigger this flood sequence to bypass reader blocking, resulting in high CPU usage, and Denial of Service (DoS).Denial of Service (Panic) in xDS RBAC Engine via Unsupported Fields inside NOT Rules
NOTrule wrapped an unsupported or unhandled field (such asSourcedMetadata), the recursive step returned an empty matcher. This could result in a runtime panic when the RBAC engine attempts to authorize an incoming request.An attacker or misconfigured/malicious xDS management server delivering an LDS/RDS update containing a
NOTrule around an unhandled field causes the gRPC server process to crash immediately (CWE-248 / Denial of Service).Patches
Has the problem been patched? What versions should users upgrade to?
All three issues have been fixed in
masterand will be released in 1.82.1 shortly.Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
If upgrading grpc-go immediately is not possible, apply the following workarounds based on your deployment architecture:
Metadata,RequestedServerName, orNOTrules wrapping unsupported fields (such asSourcedMetadata) to grpc-go servers.max_concurrent_streamslimits and active rate limiting onRST_STREAMfrequency per connection.Severity
8.27.55.9Severity
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:NReferences
This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).
Release Notes
apache/arrow-go (github.com/apache/arrow-go/v18)
v18.7.0: Apache Arrow Go v18.7.0Compare Source
What's Changed
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
Need help?
You can ask for more help in the following Slack channel: #proj-renovate-self-hosted. In that channel you can also find ADR and FAQ docs in the Resources section.