Openshift Container PlatformApplication · Redhat
CVE-2026-4647
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA flaw was found in the GNU Binutils BFD library, a widely used component for handling binary files such as object files and executables. The issue occurs when processing specially crafted XCOFF object files, where a relocation type value is not properly validated before being used. This can cause the program to read memory outside of intended bounds. As a result, affected tools may crash or expose unintended memory contents, leading to denial-of-service or limited information disclosure risks.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe GNU Binutils BFD library fails to properly validate a relocation type value when processing XCOFF (IBM AIX object file format) files, leading to an out-of-bounds memory read. This can cause tool crashes or expose limited memory contents.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Openshift Container PlatformApplication
= 4.0
Enterprise LinuxOperating system
= 6.0= 7.0= 8.0= 9.0= 10.0all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed binutils versionRun 'objdump --version' or 'readelf --version' to get the binutils version numberAffected if The version matches any of the affected Red Hat Enterprise Linux versions (6.0, 7.0, 8.0, 9.0, 10.0) or is an unpatched version of GNU Binutils
-
Verify BFD library has XCOFF supportRun 'objdump -i' or 'readelf -i' and look for 'xcoff' or 'aix' in the supported object file formats listAffected if XCOFF format is listed as a supported format, indicating the BFD library can process XCOFF files
-
Identify tools with XCOFF parsing capabilityCheck which binutils tools are available (objdump, readelf, nm, size) and note they all link against the same BFD libraryAffected if Any binutils tool that links to the vulnerable BFD library is present on the system
-
Confirm XCOFF file processing capabilityAttempt to read any XCOFF object files on the system using 'file *.o' or check if the system handles AIX binariesAffected if XCOFF object files exist on the system or the system processes AIX/XCOFF-formatted binaries
A user is affected if they have a vulnerable binutils version AND the BFD library supports XCOFF format AND they process XCOFF files (even indirectly through build tools).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate GNU Binutils to the patched version when available; until then, avoid processing untrusted XCOFF object files with affected Binutils tools.
Fix this in Openshift Container Platform
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4647 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4647 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data