CVE-2026-86805: AT_SECURE programs may load attacker-controlled code via $ORIGIN

Published Sep 22, 2026
·
Updated

A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to escalate privileges. When expanding $ORIGIN in DTRPATH for setuid/setgid (ATSECURE) programs, glibc validates the lexically normalized search path against the trusted directories but then opens the raw, un-normalized path. On systems where the Linux fs.protectedhardlinks sysctl is disabled, a local attacker who hard-links such a program into an attacker-controlled directory and wins a race to replace an intermediate path component with a symbolic link can direct the loader outside the trusted directory, causing it to load an attacker-controlled shared object and execute arbitrary code with the elevated privileges of the program.

Exploitation requires an installed setuid or setgid binary whose DTRPATH uses $ORIGIN followed by ".." traversal that normalizes into a trusted directory, and the ability to hard-link that binary and win the race by swapping a path component for a symbolic link. Major Linux-based OS distributions ship with fs.protectedhardlinks enabled by default and mitigate the vulnerability.

Affected Software

1 affected component
GNU GNU C Library (glibc)>=2.14<=2.44

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Enable the fs.protected_hardlinks sysctl on systems where it is disabled.

    Linux fs.protected_hardlinks = enabled

Event History

Sep 22, 2026
CVE Published
via MITRE·03:55 PM
Data Sourced
via MITRE·03:55 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which systems are realistically exposed?

Exposure requires glibc versions 2.14 through 2.44, an installed setuid or setgid program with a DT_RPATH containing $ORIGIN followed by ".." traversal that normalizes to a trusted directory, and fs.protected_hardlinks disabled. Major Linux-based distributions enable fs.protected_hardlinks by default, which mitigates this issue.

2

What access and conditions does an attacker need?

The attacker needs local access, the ability to create a hard link to the vulnerable privileged binary, and the ability to win a race while replacing an intermediate path component with a symbolic link. Successful exploitation can load an attacker-controlled shared object and execute code with the program's elevated privileges.

3

What can be done if glibc cannot be updated immediately?

Ensure the Linux fs.protected_hardlinks sysctl is enabled. This default setting on major Linux distributions mitigates the hard-linking condition needed for exploitation.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203