A flaw was found in binutils. A heap-buffer-overflow vulnerability exists when processing a specially crafted XCOFF (Extended Common Object File Format) object file during linking. A local attacker could trick a user into processing this malicious file, which could lead to arbitrary code execution, allowing the attacker to run unauthorized commands, or cause a denial of service, making the system unavailable.
Security readout for executives and security teams
Plain-English summary
A malicious XCOFF object file can corrupt memory when processed by affected Binutils-related tooling. An attacker must persuade a user or automated build process to handle the file. Successful exploitation could run unauthorized commands with that process’s permissions or interrupt service.
Executive priority
Prioritize remediation in CI, developer, and malware-analysis systems handling outside artifacts. The vulnerability has high potential impact but requires local file processing and user or workflow interaction. Accelerate action where untrusted objects are routinely processed; otherwise handle through the urgent patch cycle.
Technical view
CVE-2026-6846 is a CWE-122 heap-buffer overflow triggered while linking a specially crafted XCOFF object file. It is rated CVSS 3.1 7.8: local access, low complexity, no prior privileges, and user interaction required, with potentially high confidentiality, integrity, and availability impact.
Likely exposure
Confirmed affected Red Hat entries include specific Hardened Images binutils-main releases, RHEL 8 gdb and mingw-binutils, and RHEL 10 mingw-binutils. Numerous listed RHEL Binutils packages are marked unaffected. Exposure is greatest in developer, CI, analysis, or build environments that process untrusted object files.
Exploitation context
The supplied evidence does not establish active exploitation, and the CVE is not identified as being in KEV. Exploitation requires an affected tool to process an attacker-controlled XCOFF file, so untrusted source artifacts, build inputs, attachments, and analysis samples are the principal concern.
Researcher notes
Affectedness is package-specific and should not be generalized to every Binutils installation. The bundle confirms the XCOFF parsing condition and heap overflow but provides no exploitability details beyond possible code execution or denial of service. Use Red Hat’s VEX and advisories as the authoritative basis for package status.
Mitigation direction
Review RHSA-2026:33527 and RHSA-2026:39022 for applicable vendor updates.
Apply Red Hat-provided updates to confirmed affected packages and images.
Restrict affected tooling from processing untrusted XCOFF object files until updated.
Isolate build and analysis workloads that must handle externally supplied object files.
Validation and detection
Inventory Binutils, GDB, MinGW Binutils, and Hardened Images across development and CI environments.
Compare installed packages and image releases against Red Hat’s CVE and VEX status.
Confirm applicable RHSA updates are installed using approved asset-management evidence.
Identify workflows accepting object files from external or otherwise untrusted sources.
Retest affected build and analysis workflows after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
7Timeline events
2ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.