# CVE-2023-26253: Memory corruption in n/a

> A stack-based buffer over-read in GlusterFS fuse-bridge allows attackers to cause denial of service or potentially execute code.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Feb 2023
- **Updated:** 14 Mar 2025
- **Also known as:** AZL-38152, DEBIAN-CVE-2023-26253, GHSA-696f-v7g7-q758, OESA-2023-1170, UBUNTU-CVE-2023-26253, USN-5989-1, USN-6157-1

## What is CVE-2023-26253?

CVE-2023-26253 is a high-severity memory corruption vulnerability in n/a, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Gluster GlusterFS 11.0, there is an xlators/mount/fuse/src/fuse-bridge.c notify stack-based buffer over-read.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2023-26253?

It affects 1 product.


Products: Gluster Glusterfs.

## How do I fix CVE-2023-26253?

Apply the vendor's patch.

## Is CVE-2023-26253 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26253 exists.

## Other vulnerabilities in n/a

- [CVE-2018-1112](https://insights.sbomify.com/CVE-2018-1112/): Auth bypass in glusterfs (high 8.0)
- [CVE-2022-48340](https://insights.sbomify.com/CVE-2022-48340/): Use after free in n/a (high 7.5)
- [CVE-2018-10924](https://insights.sbomify.com/CVE-2018-10924/): Denial of service in glusterfs (medium 5.3)
- [CVE-2014-3619](https://insights.sbomify.com/CVE-2014-3619/): Denial of service in n/a (medium 5.0)
- [CVE-2012-4417](https://insights.sbomify.com/CVE-2012-4417/): Path traversal in n/a (low 3.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-26253 and fix it if it is affected.

What it is: CVE-2023-26253 is a high-severity memory corruption vulnerability in n/a, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-26253 exists.

Affected product: n/a. 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-2023-26253/ (Markdown: https://insights.sbomify.com/CVE-2023-26253/index.md)
```

## Sources

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

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