CVE-2026-39883

HIGHNVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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 week
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

A fix is available — apply it.

OpenTelemetry-Go is the Go implementation of OpenTelemetry. From 1.15.0 to 1.42.0, the fix for CVE-2026-24051 changed the Darwin ioreg command to use an absolute path but left the BSD kenv command using a bare name, allowing the same PATH hijacking attack on BSD and Solaris platforms. This vulnerability is fixed in 1.43.0.

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

Published

April 8, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Jun 15, 2026
Patch available. Sources: github_release, github.
github Patch Available

Incomplete fix for GHSA-9h8m-3fm2-qjrq: BSD kenv command not using absolute path enables PATH hijacking · Advisory · open-telemetry/opentelemetry-go · GitHub

https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-hfvc-g4fc-pqhx
github_release Patch Available

v1.43.0/v0.65.0/v0.19.0

Patch available: open-telemetry/opentelemetry-go v1.43.0

http://github.com/open-telemetry/opentelemetry-go/releases/tag/v1.43.0

Vendor Advisories for CVE-2026-39883(6)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcert-manager/cert-manager-istio-csr-rhel9:17883485942026-09-03redhat
redhatworkload-availability/fence-agents-remediation-rhel9-operator:17852030792026-08-12redhat
redhatworkload-availability/storage-based-remediation-rhel9-operator:17852034742026-08-12redhat
redhatodf4/rook-ceph-rhel9-operator:17829342842026-07-09redhat
redhatmulticluster-engine/assisted-service-8-rhel8:17815396912026-06-16redhat
redhatmulticluster-engine/assisted-service-9-rhel9:17815397252026-06-16redhat

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
go.opentelemetry.io/otel/sdk—1.43.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 41× 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 175 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-39883?
CVE-2026-39883 is a high vulnerability published on April 8, 2026. OpenTelemetry-Go is the Go implementation of OpenTelemetry. From 1.15.0 to 1.42.0, the fix for CVE-2026-24051 changed the Darwin ioreg command to use an absolute path but left the BSD kenv command using a bare name, allowing the same PATH hijacking attack on BSD and Solaris platforms. This…
When was CVE-2026-39883 disclosed?
CVE-2026-39883 was first published in the National Vulnerability Database on April 8, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-39883 actively exploited?
CVE-2026-39883 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 82.5% of all scored CVEs.
What is the CVSS score of CVE-2026-39883?
CVE-2026-39883 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-39883?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-39883, 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-39883

Explore →

Is Your Infrastructure Affected by CVE-2026-39883?

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

Start Free Scan →Browse All CVEs