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
Trending — 3 sources updated this weekElevated
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 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)
EPSS
6.4%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 18, 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

Vendor Advisories for CVE-2026-45287(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

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

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
go.opentelemetry.io/otel/schema/v1.0—0.0.17—
go.opentelemetry.io/otel/schema/v1.1—0.0.17—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 57× 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.

  1. 2026-07-16 02:52 UTCEG score recompute
  2. 2026-07-16 02:52 UTCVendor advisory
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-13 22:30 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 19:49 UTCEG score recompute
  9. 2026-07-11 19:49 UTCVendor advisory
  10. 2026-07-11 08:27 UTCEPSS rescore
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 18:06 UTCEG score recompute
  13. 2026-07-08 18:06 UTCVendor advisory
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-02 10:27 UTCEG score recompute
  21. 2026-07-02 10:27 UTCVendor advisory
  22. 2026-07-01 15:07 UTCEPSS rescore
  23. 2026-07-01 02:50 UTCEG score recompute
  24. 2026-07-01 02:50 UTCVendor advisory
  25. 2026-06-30 23:22 UTCEPSS rescore
Show 52 more
  1. 2026-06-29 19:41 UTCEG score recompute
  2. 2026-06-29 19:41 UTCVendor advisory
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-29 14:06 UTCEPSS rescore
  5. 2026-06-28 17:28 UTCEG score recompute
  6. 2026-06-28 17:28 UTCVendor advisory
  7. 2026-06-28 14:07 UTCEPSS rescore
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-27 18:05 UTCEG score recompute
  11. 2026-06-27 18:05 UTCVendor advisory
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-26 16:44 UTCEG score recompute
  14. 2026-06-26 16:44 UTCVendor advisory
  15. 2026-06-25 16:04 UTCEG score recompute
  16. 2026-06-25 16:04 UTCVendor advisory
  17. 2026-06-25 13:49 UTCEPSS rescore
  18. 2026-06-24 16:31 UTCEG score recompute▲ 3.40
  19. 2026-06-24 16:31 UTCVendor advisory
  20. 2026-06-24 14:05 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-22 14:25 UTCEPSS rescore
  23. 2026-06-22 14:25 UTCEPSS rescore
  24. 2026-06-21 14:56 UTCEPSS rescore
  25. 2026-06-21 14:56 UTCEPSS rescore
  26. 2026-06-21 01:59 UTCEPSS rescore
  27. 2026-06-19 19:25 UTCEPSS rescore
  28. 2026-06-18 17:52 UTCEPSS rescore
  29. 2026-06-18 17:52 UTCEPSS rescore
  30. 2026-06-18 15:52 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  31. 2026-06-17 17:53 UTCEPSS rescore
  32. 2026-06-16 17:52 UTCEPSS rescore
  33. 2026-06-16 07:34 UTCEG score recompute
  34. 2026-06-15 17:49 UTCEPSS rescore
  35. 2026-06-13 23:00 UTCEPSS rescore
  36. 2026-06-13 06:17 UTCEG score recompute
  37. 2026-06-12 23:12 UTCEPSS rescore
  38. 2026-06-12 23:12 UTCEPSS rescore
  39. 2026-06-11 14:00 UTCEPSS rescore
  40. 2026-06-10 22:18 UTCEPSS rescore
  41. 2026-06-10 13:22 UTCEPSS rescore
  42. 2026-06-10 13:22 UTCEPSS rescore
  43. 2026-06-10 04:57 UTCEG score recompute
  44. 2026-06-08 14:17 UTCEPSS rescore
  45. 2026-06-08 14:17 UTCEPSS rescore
  46. 2026-06-07 15:25 UTCEPSS rescore
  47. 2026-06-07 15:25 UTCEPSS rescore
  48. 2026-06-07 03:40 UTCEG score recompute▲ 2.10
  49. 2026-06-06 13:47 UTCEPSS rescore
  50. 2026-06-06 13:47 UTCEPSS rescore
  51. 2026-06-05 22:47 UTCEPSS rescore
  52. 2026-05-28 18:06 UTCEG score recompute

Related CVEs(same vendor + same CWE)

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 June 18, 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 6.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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.

Start Free Scan →Browse All CVEs