CVE-2026-45287

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 94% 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
Elevated
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.0.17, go.opentelemetry.io/otel/schema/v1.0 and go.opentelemetry.io/otel/schema/v1.1 leaks one file descriptor on each successful ParseFile call. ParseFile opens the schema file and passes it to Parse without closing it; repeated parsing in a long-running process can exhaust the process file descriptor limit and cause denial of service. Exploitation depends on a consuming application exposing repeated schema parsing to an attacker-controlled path. Version 0.0.17 contains a patch for the issue.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
41(Track)
EG Risk 41/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
Severity55% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

May 28, 2026

Last Modified

July 22, 2026

Advisory Details (3)

Auto-updated Jun 18, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Schema ParseFile leaks file descriptors on each parse · Advisory · open-telemetry/opentelemetry-go · GitHub

https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-995v-fvrw-c78m
github_commit

commit f12d198f161b (open-telemetry/opentelemetry-go)

Fix landed in open-telemetry/opentelemetry-go commit f12d198f161b — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-go/commit/f12d198f161b61735d65705248715aa97021ba8d
github_commit

commit e72a235518cb (open-telemetry/opentelemetry-go)

Fix landed in open-telemetry/opentelemetry-go commit e72a235518cb — awaiting tagged release

https://github.com/open-telemetry/opentelemetry-go/commit/e72a235518cb773137efd80336a179028bc34684

Patch Availability(10)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkubernetes1-35-main-1.35.6-1.hum12026-06-12redhat
redhatcaddy-main-2.11.4-0.1.hum12026-06-11redhat
redhatcosign-main-3.1.1-0.1.hum12026-06-10redhat
redhatsyft-main-1.45.1-0.1.hum12026-06-10redhat
redhathugo-main-0.162.1-1.hum12026-06-08redhat
redhatbuildah-main-1.44.0-1.hum12026-06-04redhat
redhatskopeo-main-1.23.0-1.hum12026-05-27redhat
redhatpodman-main-5.8.2-1.1.hum12026-05-09redhat
redhattrivy-main-0.69.3-1.2.hum12026-05-09redhat
redhatcontainers-common-main-0.67.0-1.1.hum12026-04-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(6 across 4 ecosystems)
Go(3)
PackageVulnerable rangeFixed inDependents
go.opentelemetry.io/otel/schema0.0.17
go.opentelemetry.io/otel/schema/v1.00.0.17
go.opentelemetry.io/otel/schema/v1.10.0.17
Debian:12(1)
PackageVulnerable rangeFixed inDependents
golang-opentelemetry-otel1.1.0-2 ... 1.43.0-4 (19 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
golang-opentelemetry-otel1.31.0-4 ... 1.43.0-4 (7 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-opentelemetry-otel1.31.0-4 ... 1.43.0-4 (7 versions)

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 49× 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 152 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45287?
CVE-2026-45287 is a medium vulnerability published on May 28, 2026. OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.0.17, go.opentelemetry.io/otel/schema/v1.0 and go.opentelemetry.io/otel/schema/v1.1 leaks one file descriptor on each successful ParseFile call. ParseFile opens the schema file and passes it to Parse without closing it;…
When was CVE-2026-45287 disclosed?
CVE-2026-45287 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45287 actively exploited?
CVE-2026-45287 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 93.7% of all scored CVEs.
What is the CVSS score of CVE-2026-45287?
CVE-2026-45287 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-45287?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45287, 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-45287

Explore →

Is Your Infrastructure Affected by CVE-2026-45287?

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