# CVE-2026-41483: Unbounded HTTP response body read in OpenTelemetry.Resources.Azure

> An attacker can cause a denial of service by forcing the Azure VM resource detector to consume excessive memory via large HTTP responses.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-vc24-j8c5-2vw4

## What is CVE-2026-41483?

CVE-2026-41483 is a medium-severity denial of service vulnerability in open-telemetry opentelemetry-dotnet-contrib, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenTelemetry.Resources.Azure is the .NET resource detector for Azure environments. In versions 1.15.0-beta.1 and earlier, the AzureVmMetaDataRequestor class makes HTTP requests to the Azure VM instance metadata service and reads the response body into memory without any size limit. An attacker who controls the configured endpoint, or who can intercept traffic to it via a man-in-the-middle attack, can return an arbitrarily large response body. This causes unbounded heap allocation in the consuming process, leading to high transient memory pressure, garbage-collection stalls, or an OutOfMemoryException that terminates the process. As a workaround, disable the Azure VM resource detector or use network-level controls such as firewall rules, mTLS, or a service mesh to prevent man-in-the-middle attacks on the Azure VM instance metadata endpoint. This issue is fixed in version 1.15.1-beta.1, which streams responses rather than buffering them entirely in memory and ignores responses larger than 4 MiB.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-41483?

2 open source packages ship an affected version, including OpenTelemetry.Resources.Azure. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `OpenTelemetry.Resources.Azure` | NuGet | All versions | 1.15.1-beta.1 |
| `OpenTelemetry.Resources.Azure` | NuGet | All versions | 1.15.1-beta.1 |

Products: Opentelemetry Opentelemetry.resources.azure.

## How do I fix CVE-2026-41483?

Upgrade OpenTelemetry.Resources.Azure to 1.15.1-beta.1 or later.

## Is CVE-2026-41483 being exploited?

There is no known exploitation of CVE-2026-41483 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41483 and fix it if it is affected.

What it is: CVE-2026-41483 is a medium-severity denial of service vulnerability in open-telemetry opentelemetry-dotnet-contrib, published on 6 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41483 in the wild and no public exploit code.

Affected packages and fixed versions:
- OpenTelemetry.Resources.Azure (NuGet): affected all versions; fixed in 1.15.1-beta.1
- OpenTelemetry.Resources.Azure (NuGet): affected all versions; fixed in 1.15.1-beta.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41483/ (Markdown: https://insights.sbomify.com/CVE-2026-41483/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41483
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41483
- OSV: https://osv.dev/vulnerability/CVE-2026-41483

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41483/
Summaries are generated and may contain mistakes; the official description above is the record.