OpenTelemetry.Resources.Azure has an unbounded HTTP response body read

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-41483: 0.32% estimated exploitation activity in the next 30 days; percentile 25.32 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary OpenTelemetry.Resources.Azure reads unbounded HTTP response bodies from the Azure VM remote instance metadata service endpoint into memory. This would allow an attacker-controlled endpoint or one acting as a Man-in-the-Middle (MitM) to cause excessive memory allocation and possible process termination (via Out of Memory (OOM)). Details The AzureVmMetaDataRequestor class makes HTTP requests to the relevant Azure VM instance metadata service (http://169.254.169.254) to obtain metadata about the running process and its infrastructure. An attacker who controls the configured endpoint, or who can intercept traffic to them (MiTM), 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. Impact Denial of Service (DoS). An attacker can destabilize or crash the application by forcing unbounded memory…

Published by the source

29 Apr 2026, 18:30 UTC

Last modified by the source

8 May 2026, 19:32 UTC

Source last checked

26 Oct 2026, 17:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-vc24-j8c5-2vw4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41483

Advisory: OpenTelemetry.Resources.Azure has an unbounded HTTP response body read
IDs: CVE-2026-41483, GHSA-vc24-j8c5-2vw4
Record: https://patchnext.com/advisories/cve-2026-41483 (revision 1, source checked 26 Oct 2026, 17:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: opentelemetry.resources.azure 1.15.1-beta.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet opentelemetry.resources.azure: affected <= 1.15.0-beta.1; fixed in 1.15.1-beta.1

## Suggested inspection (read-only)
- NuGet opentelemetry.resources.azure: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on opentelemetry.resources.azure.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-vc24-j8c5-2vw4 (GitHub-reviewed advisory GHSA-vc24-j8c5-2vw4 lists affected ranges: NuGet opentelemetry.resources.azure >=0 <=1.15.0-beta.1)

Commands are suggestions: review each one before running it.