CVE-2026-40182

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

April 23, 2026

Last Modified

April 29, 2026

Advisory Details (4)

Auto-updated Aug 2, 2026
Patch available. Sources: github_pr, github.
github_pr Patch Available

docs: add response size limitation

Patch available: open-telemetry/opentelemetry-proto v1.11.0 (PR #781 merged 2026-04-07)

https://github.com/open-telemetry/opentelemetry-proto/pull/781
github Patch Available

OTLP exporter reads unbounded HTTP response bodies · Advisory · open-telemetry/opentelemetry-dotnet · GitHub

https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-q834-8qmm-v933
github_pr

[OTLP] Limit response body size read by exporters

Fix merged in open-telemetry/opentelemetry-dotnet PR #7017 on 2026-04-06 — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-dotnet/pull/7017
github_pr

[OTLP] Refactor OpenTelemetry Collector integration tests and log HTTP response when export fails

Fix merged in open-telemetry/opentelemetry-dotnet PR #6564 on 2025-10-07 — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-dotnet/pull/6564

Affected Packages

(1 across 1 ecosystem)
NuGet(1)
PackageVulnerable rangeFixed inDependents
OpenTelemetry.Exporter.OpenTelemetryProtocol1.13.1, 1.14.0, 1.15.0, 1.15.11.15.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 156 total refreshes for this CVE.

  1. 2026-09-15 03:11 UTCEPSS rescore
  2. 2026-09-13 16:47 UTCEPSS rescore
  3. 2026-09-12 15:01 UTCEPSS rescore
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 09:37 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:01 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-04 03:29 UTCOSV refresh
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:53 UTCEPSS rescore
  14. 2026-09-01 04:39 UTCEPSS rescore
  15. 2026-08-30 19:17 UTCEPSS rescore
  16. 2026-08-30 01:22 UTCEPSS rescore
  17. 2026-08-28 21:41 UTCEPSS rescore
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-26 14:46 UTCEPSS rescore
  20. 2026-08-25 13:49 UTCEPSS rescore
  21. 2026-08-23 00:19 UTCEPSS rescore
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-19 17:03 UTCEPSS rescore
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 14:58 UTCEG score recompute
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 05:53 UTCEG score recompute
  5. 2026-08-16 02:14 UTCEPSS rescore
  6. 2026-08-15 01:30 UTCEPSS rescore
  7. 2026-08-14 04:14 UTCEG score recompute
  8. 2026-08-13 22:00 UTCEPSS rescore
  9. 2026-08-12 23:27 UTCEG score recompute
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-12 00:50 UTCEG score recompute
  12. 2026-08-11 13:43 UTCEPSS rescore
  13. 2026-08-11 02:14 UTCEG score recompute
  14. 2026-08-11 00:00 UTCEPSS rescore
  15. 2026-08-10 02:03 UTCEG score recompute
  16. 2026-08-09 13:46 UTCEPSS rescore
  17. 2026-08-09 03:25 UTCEG score recompute
  18. 2026-08-08 16:37 UTCEPSS rescore
  19. 2026-08-07 20:23 UTCEG score recompute
  20. 2026-08-06 21:47 UTCEG score recompute
  21. 2026-08-06 13:46 UTCEPSS rescore
  22. 2026-08-05 22:59 UTCEG score recompute
  23. 2026-08-05 19:17 UTCEPSS rescore
  24. 2026-08-04 15:10 UTCEPSS rescore
  25. 2026-08-04 10:38 UTCEPSS rescore
  26. 2026-08-03 21:10 UTCEG score recompute
  27. 2026-08-03 10:36 UTCEPSS rescore
  28. 2026-08-02 11:54 UTCEG score recompute
  29. 2026-08-02 02:27 UTCEPSS rescore
  30. 2026-08-01 04:16 UTCEPSS rescore
  31. 2026-07-30 16:28 UTCEPSS rescore
  32. 2026-07-30 01:30 UTCEPSS rescore
  33. 2026-07-27 14:13 UTCEPSS rescore
  34. 2026-07-26 14:54 UTCEPSS rescore
  35. 2026-07-26 14:54 UTCEPSS rescore
  36. 2026-07-25 14:18 UTCEPSS rescore
  37. 2026-07-25 14:18 UTCEPSS rescore
  38. 2026-07-24 14:17 UTCEPSS rescore
  39. 2026-07-24 14:17 UTCEPSS rescore
  40. 2026-07-23 14:18 UTCEPSS rescore
  41. 2026-07-23 14:18 UTCEPSS rescore
  42. 2026-07-23 03:11 UTCEG score recompute
  43. 2026-07-22 14:08 UTCEPSS rescore
  44. 2026-07-21 15:24 UTCEPSS rescore
  45. 2026-07-20 17:08 UTCEPSS rescore
  46. 2026-07-19 23:38 UTCOSV refresh
  47. 2026-07-19 14:31 UTCEPSS rescore
  48. 2026-07-19 02:29 UTCEPSS rescore
  49. 2026-07-18 10:04 UTCEPSS rescore
  50. 2026-07-16 17:03 UTCEPSS rescore
  51. 2026-07-15 16:57 UTCEPSS rescore
  52. 2026-07-15 16:57 UTCEPSS rescore
  53. 2026-07-15 02:00 UTCEPSS rescore
  54. 2026-07-13 22:30 UTCEPSS rescore
  55. 2026-07-13 06:13 UTCEPSS rescore
  56. 2026-07-13 06:13 UTCEPSS rescore
  57. 2026-07-12 05:46 UTCEPSS rescore
  58. 2026-07-11 08:27 UTCEPSS rescore
  59. 2026-07-09 19:10 UTCEPSS rescore
  60. 2026-07-08 15:15 UTCEPSS rescore
  61. 2026-07-07 13:46 UTCEPSS rescore
  62. 2026-07-06 16:27 UTCEPSS rescore
  63. 2026-07-06 16:27 UTCEPSS rescore
  64. 2026-07-06 02:23 UTCEPSS rescore
  65. 2026-07-06 02:23 UTCEPSS rescore
  66. 2026-07-05 02:30 UTCEPSS rescore
  67. 2026-07-04 06:31 UTCEPSS rescore
  68. 2026-07-01 15:06 UTCEPSS rescore
  69. 2026-06-30 23:22 UTCEPSS rescore
  70. 2026-06-29 14:06 UTCEPSS rescore
  71. 2026-06-28 14:07 UTCEPSS rescore
  72. 2026-06-28 04:56 UTCEPSS rescore
  73. 2026-06-27 03:08 UTCEPSS rescore
  74. 2026-06-25 13:49 UTCEPSS rescore
  75. 2026-06-25 13:49 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-40182?
CVE-2026-40182 is a medium vulnerability published on April 23, 2026. 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…
When was CVE-2026-40182 disclosed?
CVE-2026-40182 was first published in the National Vulnerability Database on April 23, 2026, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40182 actively exploited?
CVE-2026-40182 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.0% of all scored CVEs.
What is the CVSS score of CVE-2026-40182?
CVE-2026-40182 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-40182?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40182, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40182

Explore →

Is Your Infrastructure Affected by CVE-2026-40182?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs