CVE-2026-19548

Multiple Use-After-Free vulnerabilities were found in the add_archive_element function in ld/ldmain.c of the GNU linker (ld), a component of binutils. The root cause is that plugin_maybe_claim() in ld/plugin.c frees the original BFD object via bfd_close/_bfd_delete_bfd when entry->the_bfd->my_archive == NULL, but the caller retains both the original abfd parameter and a shallow copy (orig_input.the_bfd) as dangling pointers. These dangling pointers are subsequently dereferenced at three distinct locations in add_archive_element: 1. Line ~1442: accessing abfd->my_archive via bfd_usrdata(abfd->my_archive) 2. Line ~1493: multiple accesses to abfd and abfd->my_archive in a conditional check and bfd_get_filename call 3. Line ~1525: dereferencing the shallow copy orig_input.the_bfd->my_archive in trace/verbose logging The vulnerability is triggered when LTO plugins are active (link_info.lto_plugin_active is true) and the input object has abfd->my_archive == NULL, which is a valid state for standalone object files. Red Hat builds binutils with --enable-plugins and --enable-lto, confirming the vulnerable code path is compiled in and reachable. An attacker who can supply a crafted object or archive file to a build process using LTO-enabled linking could exploit this flaw to cause a denial of service (linker crash via segmentation fault). Arbitrary code execution is theoretically possible through heap manipulation but is substantially mitigated by hardening measures including stack protector, FORTIFY_SOURCE, ASLR, and PIE. The attack surface is limited to build-time environments — the linker is a development tool not exposed in production runtime. The most realistic exploitation scenario is a supply chain attack introducing a crafted object file as a build dependency in CI/CD pipelines or development environments.

• CWE-416

• https://access.redhat.com/security/cve/CVE-2026-19548Vendor Advisory
• https://bugzilla.redhat.com/show_bug.cgi?id=2507832Issue Tracking

Published

Aug 12, 2026

Last Modified

Sep 1, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-19535Nozomi Networks Labs identified a CWE-352: Cross-Site Reques…8.6
• CVE-2026-19538The BLOCKED access control list items that are evaluated to …7.5
• CVE-2026-19539Authorization Bypass Through User-Controlled Key in the tick…8.6
• CVE-2026-19542Calling tdelete on a sufficiently deep tree in the GNU C Lib…5.6
• CVE-2026-19543IBM Common Licensing Agent 9.0, Agent 9.0.0.1, Agent 9.0.0.2…6.2
• CVE-2026-19546A flaw was found in DBI. This is a fix for a partial fix for…8.8
• CVE-2026-19550A flaw was found in FreeIPA. The trust-fetch-domains command…8.2
• CVE-2026-19556Use after free in V8 in Google Chrome prior to 151.0.7922.13…8.8
• CVE-2026-19557Use after free in TabStrip in Google Chrome on Mac prior to …8.3
• CVE-2026-19558Use after free in Extensions in Google Chrome prior to 151.0…7.5
• CVE-2026-19559Use after free in HTML in Google Chrome prior to 151.0.7922.…8.8
• CVE-2026-19560Use after free in Blink in Google Chrome prior to 151.0.7922…8.8