fix: bump go.opentelemetry.io/otel/sdk to v1.43.0 to resolve CVE-2026…

[sammedsingalkar09]

Upgrades otel/sdk and all related OpenTelemetry packages from v1.40.0 to v1.43.0 to address GO-2026-4394 / CVE-2026-24051 Also bumps otel exporters, proto/otlp, and transitive dependencies updated by go mod tidy.

What type of PR is this?
/kind bug

What this PR does / why we need it:
Bumps go.opentelemetry.io/otel/sdk and all related OpenTelemetry packages from v1.40.0 to v1.43.0 to address CVE-2026-24051 (GO-2026-4394), an arbitrary code execution vulnerability via PATH hijacking on macOS. The vulnerability exists in sdk/resource/host_id.go which executes ioreg using an untrusted PATH, allowing a local attacker to place a malicious binary earlier in the search path to achieve arbitrary code execution within the application context.

Which issue(s) this PR fixes:
Fixes https://pkg.go.dev/vuln/GO-2026-4394

Special notes for your reviewer:
This is a dependency-only change. No source code was modified — only go.mod and go.sum. All otel packages are bumped together to maintain version consistency across the SDK, metric, trace, and exporter sub-modules.

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign cartermckinnon for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Welcome @sammedsingalkar09!

It looks like this is your first PR to kubernetes/cloud-provider-aws 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/cloud-provider-aws has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @sammedsingalkar09. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

PR needs rebase.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[kmala]

/triage accepted