# CVE-2025-10158: Rsync: Out of bounds array access via negative index

> A malicious rsync client can trigger an out-of-bounds heap read via a negative index, potentially causing information disclosure or crashes.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Nov 2025
- **Updated:** 19 Nov 2025
- **Also known as:** ALPINE-CVE-2025-10158, ALSA-2026:6390, ALSA-2026:6436, ALSA-2026:6825, AZL-70387, AZL-70667, BELL-CVE-2025-10158, CLSA-2026-1775723827, DEBIAN-CVE-2025-10158, ECHO-df75-75a7-da98, GHSA-3rvc-qcwh-fhqv, JLSEC-2026-625, MGASA-2026-0048, OESA-2026-1172, OESA-2026-1173, OESA-2026-1174, OESA-2026-1175, OESA-2026-1176, OESA-2026-1177, RHSA-2026:6390, RHSA-2026:6436, RHSA-2026:6825, RLSA-2026:6390, RLSA-2026:6436, RLSA-2026:6825, SUSE-SU-2025:4511-1, SUSE-SU-2026:0005-1, SUSE-SU-2026:0041-1, SUSE-SU-2026:0069-1, SUSE-SU-2026:20044-1, SUSE-SU-2026:20058-1, UBUNTU-CVE-2025-10158, openSUSE-SU-2025:15827-1

## What is CVE-2025-10158?

CVE-2025-10158 is a medium-severity memory corruption vulnerability in rsync, published on 18 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A malicious client acting as the receiver of an rsync file transfer can trigger an out of bounds read of a heap based buffer, via a negative array index. The 

malicious 

rsync client requires at least read access to the remote rsync module in order to trigger the issue.

Weakness: CWE-129 (Improper Validation of Array Index)

## Which versions are affected by CVE-2025-10158?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rsync-daemon` | AlmaLinux:10 | All versions | 3.4.1-2.el10_1.2 |
| `rsync-rrsync` | AlmaLinux:10 | All versions | 3.4.1-2.el10_1.2 |
| `rsync` | AlmaLinux:8 | All versions | 3.1.3-24.el8_10 |
| `rsync-daemon` | AlmaLinux:8 | All versions | 3.1.3-24.el8_10 |
| `rsync` | AlmaLinux:9 | All versions | 3.2.5-3.el9_7.2 |
| `rsync-daemon` | AlmaLinux:9 | All versions | 3.2.5-3.el9_7.2 |
| `rsync-rrsync` | AlmaLinux:9 | All versions | 3.2.5-3.el9_7.2 |
| `rsync` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.4.1-2.el10_1.2 |
| `rsync-daemon` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.4.1-2.el10_1.2 |
| `rsync-debuginfo` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.4.1-2.el10_1.2 |
| `rsync-debugsource` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.4.1-2.el10_1.2 |
| `rsync-rrsync` | Red Hat:enterprise_linux:10.1 | All versions | 0:3.4.1-2.el10_1.2 |
| `rsync` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.1.3-24.el8_10 |
| `rsync-daemon` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.1.3-24.el8_10 |
| `rsync-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.1.3-24.el8_10 |
| `rsync-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:3.1.3-24.el8_10 |
| `rsync-daemon` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.5-3.el9_7.2 |
| `rsync-rrsync` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.5-3.el9_7.2 |
| `rsync` | Red Hat:enterprise_linux:9::baseos | All versions | 0:3.2.5-3.el9_7.2 |
| `rsync-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:3.2.5-3.el9_7.2 |
| `rsync-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:3.2.5-3.el9_7.2 |
| `rsync` | Rocky Linux:10 | All versions | 0:3.4.1-2.el10_1.2 |
| `rsync` | Rocky Linux:8 | All versions | 0:3.1.3-24.el8_10 |
| `rsync` | Rocky Linux:9 | All versions | 0:3.2.5-3.el9_7.2 |
| `rsync` | SUSE:Linux Enterprise Micro 5.2 | All versions | 3.2.3-150000.4.39.1 |
| `rsync` | SUSE:Linux Enterprise Micro 5.3 | All versions | 3.2.3-150400.3.26.1 |
| `rsync` | SUSE:Linux Enterprise Micro 5.4 | All versions | 3.2.3-150400.3.26.1 |
| `rsync` | SUSE:Linux Enterprise Micro 5.5 | All versions | 3.2.3-150400.3.26.1 |
| `rsync` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 3.2.7-150600.3.14.1 |
| `rsync` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 3.1.3-3.34.1 |
| `rsync` | SUSE:Linux Micro 6.0 | All versions | 3.2.7-5.1 |
| `rsync` | SUSE:Linux Micro 6.1 | All versions | 3.3.0-slfo.1.1_4.1 |
| `rsync` | openSUSE:Leap 15.6 | All versions | 3.2.7-150600.3.14.1 |
| `rsync` | openSUSE:Tumbleweed | All versions | 3.4.1-4.1 |

## How do I fix CVE-2025-10158?

Apply the vendor's patch.

## Is CVE-2025-10158 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10158 and fix it if it is affected.

What it is: CVE-2025-10158 is a medium-severity memory corruption vulnerability in rsync, published on 18 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-10158 in the wild and no public exploit code.

Affected product: rsync. 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-2025-10158/ (Markdown: https://insights.sbomify.com/CVE-2025-10158/index.md)
```

## Sources

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

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