Uncontrolled Memory Allocation Affecting azure-functions-host package, versions <4.1051.200-r0


Severity

Recommended
0.0
medium
0
10

Snyk's Security Team recommends NVD's CVSS assessment. Learn more

Threat Intelligence

EPSS
0.3% (22nd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-AZUREFUNCTIONSHOST-17341837
  • published16 Jun 2026
  • disclosed23 Apr 2026

Introduced: 23 Apr 2026

CVE-2026-40182  (opens in a new tab)
CWE-789  (opens in a new tab)

How to fix?

Upgrade Minimos:latest azure-functions-host to version 4.1051.200-r0 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream azure-functions-host package and not the azure-functions-host package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

OpenTelemetry dotnet is a dotnet telemetry framework. From 1.13.1 to before 1.15.2, When exporting telemetry to a back-end/collector over gRPC or HTTP using OpenTelemetry Protocol format (OTLP), if the request results in a unsuccessful request (i.e. HTTP 4xx or 5xx), the response is read into memory with no upper-bound on the number of bytes consumed. This could cause memory exhaustion in the consuming application if the configured back-end/collector endpoint is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned by the response. This vulnerability is fixed in 1.15.2.

CVSS Base Scores

version 3.1