CVE-2026-6846

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-22. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
6.7%
KEV
Not listed

Published

April 22, 2026

Last Modified

July 15, 2026

Advisory Details (2)

Auto-updated Jun 4, 2026
Patch available. Sources: redhat.
redhat Patch Available

2460006 – (CVE-2026-6846) CVE-2026-6846 binutils: Binutils: Arbitrary code execution via malformed XCOFF object file processing

https://bugzilla.redhat.com/show_bug.cgi?id=2460006
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-6846

Vendor Advisories for CVE-2026-6846(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 115 total refreshes for this CVE.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-13 22:31 UTCEPSS rescore
  5. 2026-07-13 06:13 UTCEPSS rescore
  6. 2026-07-13 06:13 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 15:16 UTCEPSS rescore
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-07 13:46 UTCEPSS rescore
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 02:31 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-01 15:07 UTCEPSS rescore
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 75 more
  1. 2026-06-28 14:07 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 03:08 UTCEPSS rescore
  4. 2026-06-25 13:50 UTCEPSS rescore
  5. 2026-06-24 14:05 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-22 14:25 UTCEPSS rescore
  8. 2026-06-21 14:56 UTCEPSS rescore
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 01:59 UTCEPSS rescore
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-19 19:26 UTCEPSS rescore
  13. 2026-06-19 19:26 UTCEPSS rescore
  14. 2026-06-18 17:52 UTCEPSS rescore
  15. 2026-06-18 17:52 UTCEPSS rescore
  16. 2026-06-17 17:53 UTCEPSS rescore
  17. 2026-06-16 17:53 UTCEPSS rescore
  18. 2026-06-15 17:49 UTCEPSS rescore
  19. 2026-06-15 17:49 UTCEPSS rescore
  20. 2026-06-15 05:42 UTCVendor advisory
  21. 2026-06-15 05:42 UTCGHSA enrichment
  22. 2026-06-14 23:18 UTCEPSS rescore
  23. 2026-06-14 16:57 UTCVendor advisory
  24. 2026-06-14 16:57 UTCGHSA enrichment
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-12 23:12 UTCEPSS rescore
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-12 03:37 UTCVendor advisory
  29. 2026-06-12 03:37 UTCGHSA enrichment
  30. 2026-06-11 14:52 UTCVendor advisory
  31. 2026-06-11 14:52 UTCGHSA enrichment
  32. 2026-06-11 14:00 UTCEPSS rescore
  33. 2026-06-10 22:19 UTCEPSS rescore
  34. 2026-06-10 18:09 UTCVendor advisory
  35. 2026-06-10 18:09 UTCGHSA enrichment
  36. 2026-06-10 13:22 UTCEPSS rescore
  37. 2026-06-10 05:23 UTCVendor advisory
  38. 2026-06-10 05:23 UTCGHSA enrichment
  39. 2026-06-09 16:38 UTCVendor advisory
  40. 2026-06-09 16:38 UTCGHSA enrichment
  41. 2026-06-09 03:53 UTCVendor advisory
  42. 2026-06-09 03:53 UTCGHSA enrichment
  43. 2026-06-08 14:17 UTCEPSS rescore
  44. 2026-06-08 14:10 UTCVendor advisory
  45. 2026-06-08 14:10 UTCGHSA enrichment
  46. 2026-06-08 01:25 UTCVendor advisory
  47. 2026-06-08 01:25 UTCGHSA enrichment
  48. 2026-06-07 15:25 UTCEPSS rescore
  49. 2026-06-07 12:40 UTCVendor advisory
  50. 2026-06-07 12:40 UTCGHSA enrichment
  51. 2026-06-06 23:55 UTCVendor advisory
  52. 2026-06-06 23:55 UTCGHSA enrichment
  53. 2026-06-06 13:47 UTCEPSS rescore
  54. 2026-06-06 07:55 UTCVendor advisory
  55. 2026-06-06 07:55 UTCGHSA enrichment
  56. 2026-06-05 22:47 UTCEPSS rescore
  57. 2026-06-05 18:49 UTCVendor advisory
  58. 2026-06-05 18:49 UTCGHSA enrichment
  59. 2026-06-05 06:10 UTCEPSS rescore
  60. 2026-06-05 03:35 UTCVendor advisory
  61. 2026-06-05 03:35 UTCGHSA enrichment
  62. 2026-06-04 14:16 UTCVendor advisory
  63. 2026-06-04 14:16 UTCGHSA enrichment
  64. 2026-06-04 13:12 UTCEPSS rescore
  65. 2026-06-04 01:31 UTCVendor advisory
  66. 2026-06-04 01:31 UTCGHSA enrichment
  67. 2026-06-03 12:45 UTCVendor advisory
  68. 2026-06-03 12:45 UTCGHSA enrichment
  69. 2026-06-02 20:13 UTCEPSS rescore
  70. 2026-06-02 17:45 UTCVendor advisory
  71. 2026-06-02 17:45 UTCGHSA enrichment
  72. 2026-06-02 05:00 UTCVendor advisory
  73. 2026-06-02 05:00 UTCGHSA enrichment
  74. 2026-06-01 15:17 UTCVendor advisory
  75. 2026-06-01 15:17 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-6846?
CVE-2026-6846 is a high vulnerability published on April 22, 2026. 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,…
When was CVE-2026-6846 disclosed?
CVE-2026-6846 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6846 actively exploited?
CVE-2026-6846 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6846?
CVE-2026-6846 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-6846?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6846, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-6846

Explore →

Is Your Infrastructure Affected by CVE-2026-6846?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs