security: vulnerability remediation - #323
Open
kernel-internal[bot] wants to merge 1 commit into
Open
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9787bed. Configure here.
Remediates GHSA-9h8m-3fm2-qjrq (CVE-2026-24051, high): arbitrary code execution via PATH hijacking in the Go SDK, first patched in 1.40.0. Also covers CVE-2026-29181 (high), a baggage header CPU/allocation amplification that is only fixed in 1.41.0, so 1.40.0 alone is not enough. The SDK's default resource moved to schema 1.41.0, which made resource.Merge fail with a conflicting schema URL against our 1.37.0 semconv import and broke every test in lib/otel. Moved the import to semconv/v1.41.0; DeploymentEnvironmentName no longer exists there, so the attribute is now built from DeploymentEnvironmentNameKey. Co-authored-by: Cursor <[email protected]>
ulziibay-kernel
force-pushed
the
security/vuln-remediation
branch
from
July 31, 2026 18:07
9787bed to
d509a41
Compare
ulziibay-kernel
approved these changes
Jul 31, 2026
ulziibay-kernel
left a comment
ulziibay-kernel
left a comment
Contributor
There was a problem hiding this comment.
Bumped to otel 1.44.0 so this also covers CVE-2026-29181, which needs 1.41.0 and was not addressed by the original 1.40.0 bump. Realigned the semconv import to v1.41.0 to fix the conflicting schema URL that was breaking every lib/otel test. test and test-darwin now pass.
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.
Vulnerability Remediation
Fixed
Not Included
Deferred details
Note
Medium Risk
Touches observability export paths (OTLP/Prometheus) and bumps gRPC/crypto transitively; behavior should be equivalent but warrants smoke tests on metrics/traces/logs.
Overview
This PR upgrades OpenTelemetry and several related Go modules (notably
go.opentelemetry.io/otel/sdkfrom v1.38.0 to v1.44.0) to address GHSA-9h8m-3fm2-qjrq, with matching updates ingo.sumfor Prometheus, gRPC,golang.org/x/*, and other transitive dependencies pulled in by the bump.In
lib/otel/otel.go, semconv is moved from v1.37.0 to v1.41.0, and the deployment environment resource attribute is set viaDeploymentEnvironmentNameKey.String(cfg.Env)instead ofDeploymentEnvironmentName(cfg.Env), aligning with the newer semconv API while keeping the same telemetry resource shape.Reviewed by Cursor Bugbot for commit d509a41. Bugbot is set up for automated code reviews on this repo. Configure here.