Update to Cadence v1.10.3#963
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughBumps multiple Go module versions in ChangesDependency Version Updates
Wiring & Test Expectation Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@go.mod`:
- Around line 204-209: The go.opentelemetry.io/otel/sdk module is pinned at
v1.39.0 which is vulnerable to PATH-hijacking CVEs; update the go.mod entry for
the module (go.opentelemetry.io/otel/sdk) to at least v1.43.0 and align the
related OTEL indirect modules (e.g.,
go.opentelemetry.io/otel/exporters/otlp/otlptrace,
go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/metric,
go.opentelemetry.io/proto/otlp) to compatible, up-to-date versions, then run `go
mod tidy` and `go mod vendor` (if used) to ensure the module graph is consistent
before committing.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: f264f188-9d52-4538-b7e9-7af08e9707f3
⛔ Files ignored due to path filters (2)
go.sumis excluded by!**/*.sumtests/go.sumis excluded by!**/*.sum
📒 Files selected for processing (2)
go.modtests/go.mod
| go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.39.0 // indirect | ||
| go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.31.0 // indirect | ||
| go.opentelemetry.io/otel/metric v1.39.0 // indirect | ||
| go.opentelemetry.io/otel/sdk v1.39.0 // indirect | ||
| go.opentelemetry.io/otel/trace v1.39.0 // indirect | ||
| go.opentelemetry.io/proto/otlp v1.7.1 // indirect | ||
| go.opentelemetry.io/proto/otlp v1.9.0 // indirect |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify whether go.opentelemetry.io/otel/sdk@v1.39.0 is affected by published advisories
# and identify fixed ranges using OSV API (read-only).
set -euo pipefail
cat <<'JSON' > /tmp/osv-query.json
{
"package": {
"ecosystem": "Go",
"name": "go.opentelemetry.io/otel/sdk"
},
"version": "1.39.0"
}
JSON
curl -sS https://api.osv.dev/v1/query -d `@/tmp/osv-query.json` | jq .Repository: onflow/flow-evm-gateway
Length of output: 8530
🌐 Web query:
CVE-2026-24051 CVE-2026-39883 opentelemetry go sdk fix versions
💡 Result:
Fix versions (OpenTelemetry Go SDK): 1) CVE-2026-24051 (Path Hijacking / macOS/Darwin ioreg) Update go.opentelemetry.io/otel/sdk to v1.40.0 or later. The advisory states affected versions are >= 1.21.0 and <= 1.39.0, and the patched version is 1.40.0.[1] 2) CVE-2026-39883 (Follow-on to incomplete fix; BSD/Solaris kenv still left unqualified) Update go.opentelemetry.io/otel/sdk to v1.43.0 or later. NVD states the incomplete fix affects versions 1.15.0 to 1.42.0 and that this vulnerability is fixed in 1.43.0.[2] Practical guidance: If you’re running any 1.42.x releases, update at least to 1.43.0 to cover both the original ioreg path qualification and the remaining kenv issue.[2]
Citations:
- 1: GHSA-9h8m-3fm2-qjrq
- 2: https://advisories.gitlab.com/golang/go.opentelemetry.io/otel/sdk/CVE-2026-24051/
Upgrade go.opentelemetry.io/otel/sdk to v1.43.0 or later to address HIGH-severity PATH hijacking vulnerabilities.
go.opentelemetry.io/otel/sdk v1.39.0 (Line 207) is affected by two published HIGH-severity CVEs enabling arbitrary code execution via PATH hijacking:
- CVE-2026-24051 (GHSA-9h8m-3fm2-qjrq): Affects v1.21.0–1.39.0; fixed in v1.40.0. Exploits Darwin
ioregcommand. - CVE-2026-39883 (GHSA-hfvc-g4fc-pqhx): Affects v1.15.0–1.42.0; fixed in v1.43.0. Exploits BSD/Solaris
kenvcommand.
To address both vulnerabilities, upgrade the SDK to v1.43.0 and realign other OTEL modules before merge.
🧰 Tools
🪛 OSV Scanner (2.3.8)
[HIGH] 207-207: go.opentelemetry.io/otel/sdk 1.39.0: OpenTelemetry Go SDK Vulnerable to Arbitrary Code Execution via PATH Hijacking in go.opentelemetry.io/otel/sdk
(GO-2026-4394)
[HIGH] 207-207: go.opentelemetry.io/otel/sdk 1.39.0: OpenTelemetry Go SDK Vulnerable to Arbitrary Code Execution via PATH Hijacking
[HIGH] 207-207: go.opentelemetry.io/otel/sdk 1.39.0: opentelemetry-go: BSD kenv command not using absolute path enables PATH hijacking
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@go.mod` around lines 204 - 209, The go.opentelemetry.io/otel/sdk module is
pinned at v1.39.0 which is vulnerable to PATH-hijacking CVEs; update the go.mod
entry for the module (go.opentelemetry.io/otel/sdk) to at least v1.43.0 and
align the related OTEL indirect modules (e.g.,
go.opentelemetry.io/otel/exporters/otlp/otlptrace,
go.opentelemetry.io/otel/trace, go.opentelemetry.io/otel/metric,
go.opentelemetry.io/proto/otlp) to compatible, up-to-date versions, then run `go
mod tidy` and `go mod vendor` (if used) to ensure the module graph is consistent
before committing.
|
@turbolent The CI failure came from the following version bump: - github.com/onflow/flow-evm-bridge v0.1.0 // indirect
+ github.com/onflow/flow-evm-bridge v0.2.1 // indirectThis was updated in CI updated in f2522dd . |
|
@m-Peter Thank you for the fixes 🙏 |
Description
Automatically update to:
Summary by CodeRabbit