Categories
CVE-2026-45287 medium CVSS 5.5

Vulnerability in go.opentelemetry.io/otel/schema/v1.1 (CVE-2026-45287)

Summary

Vulnerability in go.opentelemetry.io/otel/schema/v1.1 (CVE-2026-45287). Risk of unauthorized operations or information disclosure. Exploitable via ParseFile. Mitigation: upgrade to 0.0.17 or later.

Original description

The description as published by the source.

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.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45287 has been found in go.opentelemetry.io/otel/schema/v1.1.
Attackers can target a specific entry point like ParseFile over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.5/10.
What to do: upgrade go.opentelemetry.io/otel/schema/v1.1 to 0.0.17 or later.
If unsure, ask your IT team or search "go.opentelemetry.io/otel/schema/v1.1 CVE-2026-45287" on the vendor's site.

CVE-2026-45287 (go.opentelemetry.io/otel/schema/v1.1) — CWE-772 / CVSS v3 5.5
Attack vector: local / no user interaction
Attack surface: ParseFile / Parse / os.Open / io.Reader
Patched: 0.0.17 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-772) exists in go.opentelemetry.io/otel/schema/v1.1. Attackers reach the vulnerable code path via ParseFile.

📍 Affected scope

Check the vendor advisory for the affected versions of go.opentelemetry.io/otel/schema/v1.1. Attack surface: ParseFile / Parse / os.Open / io.Reader.

🔥 Severity

Severity: Medium (CVSS 5.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.0.17.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'go.opentelemetry.io/otel/schema/v1.1' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'go.opentelemetry.io/otel/schema/v1.1' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で go.opentelemetry.io/otel/schema/v1.1 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade go.opentelemetry.io/otel/schema/v1.1 to 0.0.17

    ステージング環境で 0.0.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go go.opentelemetry.io/otel/schema/v1.1
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.17"}]}]
go go.opentelemetry.io/otel/schema/v1.0
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.17"}]}]
go go.opentelemetry.io/otel/schema
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.0.17"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details