BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-39882High confidence

OpenTelemetry-Go OTLP HTTP exporters read unbounded HTTP response bodies

open-telemetry · opentelemetry-go

Official source article: GitHub GHSA-W8RR-5GCM-PP58 ↗. Check the applicable product and release in the original source.

5.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.19% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs open-telemetry opentelemetry-go and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcegolang-opentelemetry-otelAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcegolang-opentelemetry-otelAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegolang-opentelemetry-otelVendor fix publishedDebian records a fixed source-package version for this release.1.43.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegolang-opentelemetry-otelVendor fix publishedDebian records a fixed source-package version for this release.1.43.0-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegolang-opentelemetry-otelUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges6 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Gogo.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttpSEMVER: introduced 0; fixed 0.19.00.19.0OSV record ↗aggregator derived · 10 Sep 2026
Gogo.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttpSEMVER: introduced 0; fixed 1.43.01.43.0OSV record ↗aggregator derived · 10 Sep 2026
Gogo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttpSEMVER: introduced 0; fixed 1.43.01.43.0OSV record ↗aggregator derived · 10 Sep 2026
gogo.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp< 0.19.00.19.0GitHub advisory ↗upstream repository advisory · 9 Apr 2026
gogo.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp< 1.43.01.43.0GitHub advisory ↗upstream repository advisory · 9 Apr 2026
gogo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp< 1.43.01.43.0GitHub advisory ↗upstream repository advisory · 9 Apr 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-39882 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitygithub.com/open-telemetry/opentelemetry-go: OpenTelemetry-Go: Memory exhaustion via uncapped HTTP response body reading
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • multicluster-engine/maestro-rhel9 as a component of Multicluster Engine for Kubernetes
Summary
A flaw was found in OpenTelemetry-Go. The otlp HTTP exporters read the full HTTP response body into an in-memory buffer without a size cap. A remote attacker, by controlling the collector endpoint or performing a man-in-the-middle (MITM) attack on the exporter connection, can exploit this to cause memory exhaustion. This vulnerability can lead to a Denial of Service (DoS) for the affected system.
Remediation
For OpenShift Container Platform 4.22 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/release_notes/ You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are as follows: (For x86_64 architecture) The image digest is sha256:171952b3f8295184cbc98cf89d4aed20e0fbfc06cc95e854d53e8a8a56156490 (For s390x architecture) The image digest is sha256:5d4c79493b883693cfff7222309ece89637bf606f56065d8b5c1ac26acdd2fcf (For ppc64le architecture) The image digest is sha256:7ecf7ab1db0964ab5841c89b48ec6272fe84d1428adde038d59078557752a30e (For aarch64 architecture) The image digest is sha256:4cfd7378ff6b2e188ce37a04cdca2bcf3638ab397f52fb64f92af8cb81859a5f All OpenShift Container Platform 4.22 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html-single/updating_clusters/index#updating-cluster-cli.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-20628

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

What

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

Why

The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

Why

The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

How

An attacker operating through an adjacent network may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
an adjacent network → Memory Allocation with Excessive Size Value → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Adjacent
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-789 ↗

CWE-789: Memory Allocation with Excessive Size Value. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
UnauthenticatedCWE-789
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-2334Red Hat OpenShift Container Platform (fast-uri,OpenTelemetry-Go) : Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift Container Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen oder einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260415Security Bulletin 15 April 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 15 April 2026, published on 15 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1249Multiples vulnérabilités dans les produits VMware

d?id=CVE-2026-39828 Référence CVE CVE-2026-39829 https://www.cve.org/CVERecord?id=CVE-2026-39829 Référence CVE CVE-2026-39830 https://www.cve.org/CVERecord?id=CVE-2026-39830 Référence CVE CVE-2026-39831 https://www.cve.org/CVERecord?id=CVE-2026-39831 Référence CVE CVE-2026-39832 https://www.cve.org/CVERecord?id=CVE-2026-39832 Référence CVE CVE-2026-39833 https://www.cve.org/CVERecord?id=CVE-2026-39833 Référence CVE CVE-2026-39834 https://www.cve.org/CVERecord?id=CVE-2026-39834 Référence CVE CVE-2026-39835 https://www.cve.org/CVERecord?id=CVE-2026-39835 Référence CVE CVE-2026-39836 https://www.cve.org/CVERecord?id=CVE-2026-39836 Référence CVE CVE-2026-39882 https://www.cve.org/CVERecord?id=CVE-2026-39882 Référence CVE CVE-2026-39883 https://www.cve.org/CVERecord?id=CVE-2026-39883 Référence CVE CVE-2026-41889 https://www.cve.org/CVERecord?id=CVE-2026-41889 Référence CVE CVE-2026-41989 https://www.cve.org/CVERecord?id=CVE-2026-41989 Référence CVE CVE-2026-41991 https://www.cve.org/CVERecord?id=CVE-2026-41991 Référence CVE CVE-2026-41992 https://www.cve.org/CVERecord?id=CVE-2026-41992 Référence CVE CVE-2026-42250 https://www.cve.org/CVERecord?id=CVE-2026-42250 Référence CVE CVE-2026-42499 https://www.cve.org/CVERecord?id=CVE-2026-42499 Référence CVE CVE-2026-42501 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0888Multiples vulnérabilités dans les produits Splunk

d?id=CVE-2026-28390 Référence CVE CVE-2026-29181 https://www.cve.org/CVERecord?id=CVE-2026-29181 Référence CVE CVE-2026-32280 https://www.cve.org/CVERecord?id=CVE-2026-32280 Référence CVE CVE-2026-32281 https://www.cve.org/CVERecord?id=CVE-2026-32281 Référence CVE CVE-2026-32283 https://www.cve.org/CVERecord?id=CVE-2026-32283 Référence CVE CVE-2026-32285 https://www.cve.org/CVERecord?id=CVE-2026-32285 Référence CVE CVE-2026-32287 https://www.cve.org/CVERecord?id=CVE-2026-32287 Référence CVE CVE-2026-34986 https://www.cve.org/CVERecord?id=CVE-2026-34986 Référence CVE CVE-2026-39836 https://www.cve.org/CVERecord?id=CVE-2026-39836 Référence CVE CVE-2026-39882 https://www.cve.org/CVERecord?id=CVE-2026-39882 Référence CVE CVE-2026-39883 https://www.cve.org/CVERecord?id=CVE-2026-39883 Référence CVE CVE-2026-42501 https://www.cve.org/CVERecord?id=CVE-2026-42501 Référence CVE CVE-2026-6914 https://www.cve.org/CVERecord?id=CVE-2026-6914 Référence CVE CVE-2026-6915 https://www.cve.org/CVERecord?id=CVE-2026-6915 Référence CVE CVE-2026-8053 https://www.cve.org/CVERecord?id=CVE-2026-8053 Référence CVE CVE-2026-8199 https://www.cve.org/CVERecord?id=CVE-2026-8199 Référence CVE CVE-2026-8200 https://www.cve.org/CVERecord?id=CVE-2026-8200 Référence CVE CVE-2026-8201 https://www.cve.org/CVERecord?id=CVE-2026-82

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0466Multiples vulnérabilités dans les produits Microsoft

De multiples vulnérabilités ont été découvertes dans les produits Microsoft. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-010714opentelemetryにおける過剰なサイズ値のメモリ割り当てに関する脆弱性

OpenTelemetry-GoはOpenTelemetryのGo言語による実装です。バージョン1.43.0以前では、otlp HTTPエクスポーター（トレース、メトリクス、ログ）が、サイズ制限なくHTTPレスポンスの本文全体をメモリ内のbytes.Bufferに読み込んでいました。このため、設定されたコレクターエンドポイントが攻撃者によって制御されている場合、またはネットワーク攻撃者がエクスポーターの接続を中間者攻撃できる場合に、メモリ枯渇を引き起こす悪用が可能でした。この脆弱性はバージョン1.43.0で修正されています。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
multicluster-engine/maestro-rhel9 as a component of Multicluster Engine for Kubernetes
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 8 Apr 2026 · Last source change 9 Apr 2026, 20:22 UTC · CWE-789 · Memory Allocation with Excessive Size Value

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-20628
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Fixed: registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:3f93da96bc86621030e105f78e7c38a7a2e013942d646073773fe1bc8e3e6562_ppc64le as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:499b5e936fc2cf337bbe84a3b8feb236b1e12ce038922a82a98c629f01357c7b_amd64 as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:4f4fe3eee19c9247597598a56eafdce048f7c837271cb8226ed60b87f58cdc8b_arm64 as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:619ef2d8f774dcb0a806ec9cfee5f0dd987a3a8f6d6a19e2bbd3c8c434c53275_s390x as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:a5b33d7ae151414c8e1834c4ae7cccb282675129b359eeb8bfd169fb06e502b2_s390x as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:b2ba30ffc3f5d1f2d25de0dd8a1258cd714d4b974fd8c24bf3e230374b558e04_amd64 as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:c7999a4635cbf45db6555712605d29949401d41f0a9054c1d9544dacce5b99ba_arm64 as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:dcb1429fb5f1aab6357ae619f54ff1b29befbca7a031cb4ff5a54774de15daaa_ppc64le as a component of Red Hat OpenShift Container Platform 4.22
    After
    multicluster-engine/maestro-rhel9 as a component of Multicluster Engine for Kubernetes · Fixed: registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:3f93da96bc86621030e105f78e7c38a7a2e013942d646073773fe1bc8e3e6562_ppc64le as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:499b5e936fc2cf337bbe84a3b8feb236b1e12ce038922a82a98c629f01357c7b_amd64 as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:4f4fe3eee19c9247597598a56eafdce048f7c837271cb8226ed60b87f58cdc8b_arm64 as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:619ef2d8f774dcb0a806ec9cfee5f0dd987a3a8f6d6a19e2bbd3c8c434c53275_s390x as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:a5b33d7ae151414c8e1834c4ae7cccb282675129b359eeb8bfd169fb06e502b2_s390x as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:b2ba30ffc3f5d1f2d25de0dd8a1258cd714d4b974fd8c24bf3e230374b558e04_amd64 as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:c7999a4635cbf45db6555712605d29949401d41f0a9054c1d9544dacce5b99ba_arm64 as a component of Red Hat OpenShift Container Platform 4.22; registry.redhat.io/openshift4/ose-thanos-rhel9@sha256:dcb1429fb5f1aab6357ae619f54ff1b29befbca7a031cb4ff5a54774de15daaa_ppc64le as a component of Red Hat OpenShift Container Platform 4.22
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.43.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    < 1.43.0 · Fixed: For OpenShift Container Platform 4.22 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html/release_notes/ You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha values for the release are as follows: (For x86_64 architecture) The image digest is sha256:171952b3f8295184cbc98cf89d4aed20e0fbfc06cc95e854d53e8a8a56156490 (For s390x architecture) The image digest is sha256:5d4c79493b883693cfff7222309ece89637bf606f56065d8b5c1ac26acdd2fcf (For ppc64le architecture) The image digest is sha256:7ecf7ab1db0964ab5841c89b48ec6272fe84d1428adde038d59078557752a30e (For aarch64 architecture) The image digest is sha256:4cfd7378ff6b2e188ce37a04cdca2bcf3638ab397f52fb64f92af8cb81859a5f All OpenShift Container Platform 4.22 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.22/html-single/updating_clusters/index#updating-cluster-cli.
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2026-20628↗Red Hat Product Security security advisory↗Patch or update reference↗CVE authority or vendor reference · GitHub GHSA-W8RR-5GCM-PP58↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-39882 · cve.blacktree.nl