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

jq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers

jqlang · jq

Official source article: GitHub GHSA-2HHH-PX8H-355P ↗. Check the applicable product and release in the original source.

6.9MediumCVSS 4.0
Recommended action
Within 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:High, raised one band.upgradedsince 15 Jul 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • A structured source references public exploit or proof-of-concept material.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.82% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs jqlang jq 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: Within 30 daysRemediation target: Within 180 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.

Distribution package intelligence

Release-specific package status

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

7 package states
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
Alpine v3.23v3.23 · mainjqVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.8.2-r0Alpine Security Database ↗Source updated 3 Oct 2026
Alpine v3.22v3.22 · mainjqVendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected.1.8.2-r0Alpine Security Database ↗Source updated 3 Oct 2026
Debian trixietrixie · sourcejqVendor fix publishedDebian records a fixed source-package version for this release.1.7.1-6+deb13u2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcejqVendor fix publishedDebian records a fixed source-package version for this release.1.6-2.1+deb12u2Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcejqVendor fix publishedDebian records a fixed source-package version for this release.1.8.1-5Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcejqVendor fix publishedDebian records a fixed source-package version for this release.1.8.1-5Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivejqVendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree.1.7.1-3ubuntu0.24.04.2Canonical Ubuntu Security ↗Source updated 5 Oct 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-39979 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityjq: out-of-bounds read in jv_parse_sized() on error formatting for non-NUL-terminated buffers
2 known affected

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

  • ansible-automation-platform-26/controller-rhel9 as a component of Red Hat Ansible Automation Platform 2
  • jq.src as a component of Red Hat Ceph Storage 4
Summary
A flaw was found in jq, a command line JSON processor, specifically in the libjq API. Parsing a malformed JSON input from a non-NUL-terminated buffer using the `jv_parse_sized` function can cause an out-of-bounds read, resulting in an application crash and a possible memory disclosure within the error message generated by the parser.
Remediation
For OpenShift Container Platform 4.12 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.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:4d3bbcec187be94449a001896fcd21e41580dbba1cac38717905a2cb31a94a6e All OpenShift Container Platform 4.12 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.12/html-single/updating_clusters/index#updating-cluster-within-minor.
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-22128

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 actionWithin 7 days

Medium technical severity with public exploit material referenced by a structured source; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

jq is a command-line JSON processor. In commits before 2f09060afab23fe9390cce7cb860b10416e1bf5f, the jv_parse_sized() API in libjq accepts a counted buffer with an explicit length parameter, but its error-handling path formats the input buffer using %s in jv_string_fmt(), which reads until a NUL terminator is found rather than respecting the caller-supplied length. This means that when malformed JSON is passed in a non-NUL-terminated buffer, the error construction logic performs an out-of-bounds read past the end of the buffer. The vulnerability is reachable by any libjq consumer calling jv_parse_sized() with untrusted input, and depending on memory layout, can result in memory disclosure or process termination. The issue has been patched in commit 2f09060afab23fe9390cce7cb860b10416e1bf5f.

What

jq is a command-line JSON processor. In commits before 2f09060afab23fe9390cce7cb860b10416e1bf5f, the jv_parse_sized() API in libjq accepts a counted buffer with an explicit length parameter, but its error-handling path formats the input buffer using %s in jv_string_fmt(), which reads until a NUL terminator is found rather than respecting the caller-supplied length. This means that when malformed JSON is passed in a non-NUL-terminated buffer, the error construction logic performs an out-of-bounds read past the end of the buffer. The vulnerability is reachable by any libjq consumer calling jv_parse_sized() with untrusted input, and depending on memory layout, can result in memory disclosure or process termination. The issue has been patched in commit 2f09060afab23fe9390cce7cb860b10416e1bf5f.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path 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

jq is a command-line JSON processor. In commits before 2f09060afab23fe9390cce7cb860b10416e1bf5f, the jv_parse_sized() API in libjq accepts a counted buffer with an explicit length parameter, but its error-handling path formats the input buffer using %s in jv_string_fmt(), which reads until a NUL terminator is found rather than respecting the caller-supplied length. This means that when malformed JSON is passed in a non-NUL-terminated buffer, the error construction logic performs an out-of-bounds read past the end of the buffer. The vulnerability is reachable by any libjq consumer calling jv_parse_sized() with untrusted input, and depending on memory layout, can result in memory disclosure or process termination. The issue has been patched in commit 2f09060afab23fe9390cce7cb860b10416e1bf5f.

Why

The product reads data past the end, or before the beginning, of the intended buffer.

How

An attacker operating through a network path 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.
Reference recorded

A structured CVE source labels at least one public reference as exploit material. BlackTree has not independently validated that it is safe, reliable or weaponised.

Likely attack path
a network path → Out-of-bounds Read → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-125 ↗

CWE-125: Out-of-bounds Read. The product reads data past the end, or before the beginning, of the intended buffer.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N

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

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCLowVulnerable-system confidentiality: A successful attack can cause a limited loss.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
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.
NetworkUnauthenticatedCWE-125Public exploit reference
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-1183Red Hat Hardened Images RPMs (jq und pyOpenSSL): Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat Red Hat Hardened Images RPMs ausnutzen, um Sicherheitsvorkehrungen zu umgehen, einen Denial-of-Service-Zustand verursachen, vertrauliche Informationen offenlegen oder nicht näher spezifizierte Angriffe durchführen, einschließlich potenzieller Codeausführung.

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-0986Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-31786 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-33870 https://www.cve.org/CVERecord?id=CVE-2026-33870 Référence CVE CVE-2026-33871 https://www.cve.org/CVERecord?id=CVE-2026-33871 Référence CVE CVE-2026-34477 https://www.cve.org/CVERecord?id=CVE-2026-34477 Référence CVE CVE-2026-34478 https://www.cve.org/CVERecord?id=CVE-2026-34478 Référence CVE CVE-2026-34479 https://www.cve.org/CVERecord?id=CVE-2026-34479 Référence CVE CVE-2026-34480 https://www.cve.org/CVERecord?id=CVE-2026-34480 Référence CVE CVE-2026-35177 https://www.cve.org/CVERecord?id=CVE-2026-35177 Référence CVE CVE-2026-39979 https://www.cve.org/CVERecord?id=CVE-2026-39979 Référence CVE CVE-2026-40164 https://www.cve.org/CVERecord?id=CVE-2026-40164 Référence CVE CVE-2026-4046 https://www.cve.org/CVERecord?id=CVE-2026-4046 Référence CVE CVE-2026-41254 https://www.cve.org/CVERecord?id=CVE-2026-41254 Référence CVE CVE-2026-41284 https://www.cve.org/CVERecord?id=CVE-2026-41284 Référence CVE CVE-2026-41293 https://www.cve.org/CVERecord?id=CVE-2026-41293 Référence CVE CVE-2026-41417 https://www.cve.org/CVERecord?id=CVE-2026-41417 Référence CVE CVE-2026-42496 https://www.cve.org/CVERecord?id=CVE-2026-42496 Référence CVE CVE-2026-42497 https://www.cve.org/CVERecord?id=CV

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0863Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-22990 Référence CVE CVE-2026-23191 https://www.cve.org/CVERecord?id=CVE-2026-23191 Référence CVE CVE-2026-23216 https://www.cve.org/CVERecord?id=CVE-2026-23216 Référence CVE CVE-2026-23270 https://www.cve.org/CVERecord?id=CVE-2026-23270 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31408 https://www.cve.org/CVERecord?id=CVE-2026-31408 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-35385 https://www.cve.org/CVERecord?id=CVE-2026-35385 Référence CVE CVE-2026-35535 https://www.cve.org/CVERecord?id=CVE-2026-35535 Référence CVE CVE-2026-39979 https://www.cve.org/CVERecord?id=CVE-2026-39979 Référence CVE CVE-2026-40164 https://www.cve.org/CVERecord?id=CVE-2026-40164 Référence CVE CVE-2026-41035 https://www.cve.org/CVERecord?id=CVE-2026-41035 Référence CVE CVE-2026-43027 https://www.cve.org/CVERecord?id=CVE-2026-43027 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43074 https://www.cve.org/CVERecord?id=CVE-2026-43074 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43128 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0832Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-22984 Référence CVE CVE-2026-22990 https://www.cve.org/CVERecord?id=CVE-2026-22990 Référence CVE CVE-2026-23216 https://www.cve.org/CVERecord?id=CVE-2026-23216 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31411 https://www.cve.org/CVERecord?id=CVE-2026-31411 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-35385 https://www.cve.org/CVERecord?id=CVE-2026-35385 Référence CVE CVE-2026-35535 https://www.cve.org/CVERecord?id=CVE-2026-35535 Référence CVE CVE-2026-39979 https://www.cve.org/CVERecord?id=CVE-2026-39979 Référence CVE CVE-2026-40164 https://www.cve.org/CVERecord?id=CVE-2026-40164 Référence CVE CVE-2026-41035 https://www.cve.org/CVERecord?id=CVE-2026-41035 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43112 https://www.cve.org/CVERecord?id=CVE-2026-43112 Référence CVE CVE-2026-43125 https://www.cve.org/CVERecord?id=CVE-2026-43125 Référence CVE CVE-2026-43128 https://www.cve.org/CVERecord?id=CVE-2026-43128 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0808Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-31474 Référence CVE CVE-2026-31488 https://www.cve.org/CVERecord?id=CVE-2026-31488 Référence CVE CVE-2026-31636 https://www.cve.org/CVERecord?id=CVE-2026-31636 Référence CVE CVE-2026-31641 https://www.cve.org/CVERecord?id=CVE-2026-31641 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31772 https://www.cve.org/CVERecord?id=CVE-2026-31772 Référence CVE CVE-2026-31786 https://www.cve.org/CVERecord?id=CVE-2026-31786 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-35385 https://www.cve.org/CVERecord?id=CVE-2026-35385 Référence CVE CVE-2026-39979 https://www.cve.org/CVERecord?id=CVE-2026-39979 Référence CVE CVE-2026-40164 https://www.cve.org/CVERecord?id=CVE-2026-40164 Référence CVE CVE-2026-41035 https://www.cve.org/CVERecord?id=CVE-2026-41035 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43056 https://www.cve.org/CVERecord?id=CVE-2026-43056 Référence CVE CVE-2026-43198 https://www.cve.org/CVERecord?id=CVE-2026-43198 Référence CVE CVE-2026-43260 https://www.cve.org/CVERecord?id=CVE-2026-43260 Référence CVE CVE-2026-43279 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0781Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2026-23243 Référence CVE CVE-2026-23392 https://www.cve.org/CVERecord?id=CVE-2026-23392 Référence CVE CVE-2026-23455 https://www.cve.org/CVERecord?id=CVE-2026-23455 Référence CVE CVE-2026-31532 https://www.cve.org/CVERecord?id=CVE-2026-31532 Référence CVE CVE-2026-31669 https://www.cve.org/CVERecord?id=CVE-2026-31669 Référence CVE CVE-2026-31685 https://www.cve.org/CVERecord?id=CVE-2026-31685 Référence CVE CVE-2026-31786 https://www.cve.org/CVERecord?id=CVE-2026-31786 Référence CVE CVE-2026-31787 https://www.cve.org/CVERecord?id=CVE-2026-31787 Référence CVE CVE-2026-35385 https://www.cve.org/CVERecord?id=CVE-2026-35385 Référence CVE CVE-2026-39979 https://www.cve.org/CVERecord?id=CVE-2026-39979 Référence CVE CVE-2026-40164 https://www.cve.org/CVERecord?id=CVE-2026-40164 Référence CVE CVE-2026-41035 https://www.cve.org/CVERecord?id=CVE-2026-41035 Référence CVE CVE-2026-41326 https://www.cve.org/CVERecord?id=CVE-2026-41326 Référence CVE CVE-2026-43037 https://www.cve.org/CVERecord?id=CVE-2026-43037 Référence CVE CVE-2026-43038 https://www.cve.org/CVERecord?id=CVE-2026-43038 Référence CVE CVE-2026-43110 https://www.cve.org/CVERecord?id=CVE-2026-43110 Référence CVE CVE-2026-43116 https://www.cve.org/CVERecord?id=CVE-2026-43116 Référence CVE CVE-2026-43158 https://www.cve.org/CVERecord?id=

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

sécurité Microsoft CVE-2026-31423 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31424 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31426 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31427 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31428 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-40393 du 14 avril 2026 Bulletin de sécurité Microsoft CVE-2026-32316 du 17 avril 2026 Bulletin de sécurité Microsoft CVE-2026-33947 du 17 avril 2026 Bulletin de sécurité Microsoft CVE-2026-33948 du 17 avril 2026 Bulletin de sécurité Microsoft CVE-2026-39956 du 17 avril 2026 Bulletin de sécurité Microsoft CVE-2026-39979 du 17 avril 2026 Bulletin de sécurité Microsoft CVE-2026-40164 du 17 avril 2026 Bulletin de sécurité Microsoft CVE-2025-70873 du 18 avril 2026 Une gestion de version détaillée se trouve à la fin de ce document. Risque Non spécifié par l'éditeur Systèmes affectés azl3 cups 2.4.16-1 versions antérieures à 2.4.17-1 azl3 jq 1.7.1-4 versions antérieures à 1.7.1-5 azl3 kernel 6.6.130.1-3 versions antérieures à 6.6.134.1-1 azl3 mesa 24.0.1-6 versions antérieures à 24.0.1-8 azl3 pytorch 2.2.2-12 versions antérieures à 2.2.2-14 azl3 sqlite 3.44.0-2 versions antérieures à 3.44.0-3 Résumé De multiples vulnérabilités ont été découvertes dans les produit

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-012826jqlangのjqにおける境界外読み取りに関する脆弱性

jqはコマンドラインのJSONプロセッサです。2f09060afab23fe9390cce7cb860b10416e1bf5fのコミット以前では、libjqのjv_parse_sized() APIは明示的な長さパラメータを持つカウントされたバッファを受け入れていましたが、そのエラーハンドリングパスではjv_string_fmt()内で%sを使用して入力バッファをフォーマットしており、呼び出し元が指定した長さを考慮せず、NUL終端子が見つかるまで読み取っていました。これは、NUL終端されていない不正なJSONが渡された場合に、エラー構築ロジックがバッファの終端を越えた範囲外読み取りを行ってしまうことを意味します。この脆弱性は、非信頼入力を用いてjv_parse_sized()を呼び出すすべてのlibjq利用者が到達可能であり、メモリの配置によってはメモリ情報漏洩やプロセス終了を引き起こす可能性があります。この問題はコミット2f09060afab23fe9390cce7cb860b10416e1bf5fで修正されました。

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.
Patch available
Affected
Fixed
Action
For OpenShift Container Platform 4.12 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.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:4d3bbcec187be94449a001896fcd21e41580dbba1cac38717905a2cb31a94a6e All OpenShift Container Platform 4.12 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.12/html-single/updating_clusters/index#updating-cluster-within-minor.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 13 Apr 2026 · Last source change 15 Jul 2026, 01:01 UTC · CWE-125 · Out-of-bounds Read

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-22128
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

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
    < 2f09060afab23fe9390cce7cb860b10416e1bf5f · 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
    < 2f09060afab23fe9390cce7cb860b10416e1bf5f · Fixed: For OpenShift Container Platform 4.12 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.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:4d3bbcec187be94449a001896fcd21e41580dbba1cac38717905a2cb31a94a6e All OpenShift Container Platform 4.12 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.12/html-single/updating_clusters/index#updating-cluster-within-minor.
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
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-39979 · cve.blacktree.nl