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
This is a high-severity file-processing flaw in Red Hat-packaged binutils-related components. A malicious XCOFF object file could cause code execution or denial of service if someone links or processes it. It is not remotely exploitable by itself; it needs local file processing and user interaction.
Executive priority
Treat as high priority for build and developer environments, especially where untrusted artifacts enter pipelines. It is not presented as actively exploited or network-reachable, so prioritize exposed processing workflows over broad emergency response.
Technical view
CVE-2026-6846 is a heap-buffer-overflow, CWE-122, in XCOFF object handling during linking. The supplied CVSS 3.1 score is 7.8 with local attack vector, low complexity, no privileges, required user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Most exposed systems are developer, build, CI, packaging, or analysis environments that process untrusted object files. The supplied Red Hat data marks specific Hardened Images binutils-main versions, RHEL 10 mingw-binutils, and RHEL 8 gdb and mingw-binutils as affected.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation. Practical abuse requires convincing a user or workflow to process a crafted XCOFF object file. That lowers wormability, but build systems and automated artifact processing can still create meaningful risk.
Researcher notes
Evidence is Red Hat-centered. The bundle identifies affected and unaffected Red Hat packages but does not include exploit proof, KEV status, or detailed fixed-version text. Avoid assuming all binutils deployments are affected without vendor-specific confirmation.
Mitigation direction
Apply applicable Red Hat errata where available for affected packages.
Check Red Hat CVE and CSAF VEX entries for current package status.
Restrict processing of untrusted XCOFF or object files in build workflows.
Run file-analysis and linking jobs with least privilege and isolation.
Prioritize affected CI, developer, and artifact-ingestion systems.
Validation and detection
Inventory installed binutils, mingw-binutils, gdb, and binutils-main packages.
Compare package status against the Red Hat CVE and CSAF VEX data.
Identify workflows that link or inspect externally supplied object files.
Confirm relevant RHSA advisories are applied where applicable.
Document unaffected Red Hat products separately to avoid unnecessary 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.