# CVE-2026-95818: AT_SECURE program buffer overflow via $ORIGIN processing

> A local attacker can trigger a stack buffer overflow in the glibc dynamic loader when processing specific $ORIGIN paths, causing crashes or memory disclosure in setuid programs.

- **Severity:** Low 3.6 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** AZL-103416, DEBIAN-CVE-2026-95818, ECHO-f127-8d9c-ea3a, GHSA-h8x4-734c-9753, UBUNTU-CVE-2026-95818

## What is CVE-2026-95818?

CVE-2026-95818 is a low-severity memory corruption vulnerability in The GNU C Library glibc, published on 22 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A stack-based buffer overflow in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to crash or corrupt the memory of setuid/setgid (AT_SECURE) programs.

When such a program's DT_RPATH or DT_RUNPATH begins with $ORIGIN and is followed by NUL or '/' the loader both reads past the end of the path buffer and writes past the end of a stack-allocated internal buffer. The corrupted loader stack can lead to a loader crash (denial of service) and limited disclosure of process memory.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-95818?


## How do I fix CVE-2026-95818?

Apply the vendor's patch.

## Is CVE-2026-95818 being exploited?

There is no known exploitation of CVE-2026-95818 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-95818 and fix it if it is affected.

What it is: CVE-2026-95818 is a low-severity memory corruption vulnerability in The GNU C Library glibc, published on 22 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-95818 in the wild and no public exploit code.

Affected product: The GNU C Library glibc. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-95818/ (Markdown: https://insights.sbomify.com/CVE-2026-95818/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-95818
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-95818
- OSV: https://osv.dev/vulnerability/CVE-2026-95818

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-95818/
Summaries are generated and may contain mistakes; the official description above is the record.