🛡️ CVE-2026-43618 on BellSoft — rsync

Distribution advisory

This page covers CVE-2026-43618 as tracked by BellSoft, for the package rsync. The fix is available in version 3.4.3-r0; earlier versions remain affected.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability high.

CVSS metrics in full

The score comes from this vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

• Attack vector: Network — reachable from anywhere that can route to the service.
• Attack complexity: Low — the attack works reliably, with no preparation.
• Privileges required: Low — an ordinary user account is enough.
• User interaction: None — nobody has to be tricked into anything.
• Scope: Unchanged — the damage stays inside the vulnerable component.
• Confidentiality impact: High — total loss, or loss the attacker controls.
• Integrity impact: None.
• Availability impact: High — total loss, or loss the attacker controls.

Weakness class

BELL-CVE-2026-43618 is classified as CWE-125: Out-of-bounds Read. The code reads past the limits of a buffer, exposing adjacent memory contents or crashing the process.

Affected software

BELL-CVE-2026-43618 is recorded against 1 package.

• rsync (from 3.2.5-r0 up to 3.4.3-r0)

Timeline and source

Published on 21 May 2026 and last revised on 26 May 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

docs.bell-sw.com (Advisory)

Same weakness in other software

These advisories are the same class of weakness (CWE-125: Out-of-bounds Read) in other software:

• CVE-2019-14492 (8.0 High, published 9 Jul 2026)
• CVE-2022-23594 (8.0 High, published 9 Jul 2026)
• CVE-2017-18009 (8.0 High, published 9 Jul 2026)
• CVE-2019-14491 (8.0 High, published 9 Jul 2026)
• CVE-2022-21728 (8.0 High, published 9 Jul 2026)
• CVE-2017-12599 (8.0 High, published 9 Jul 2026)
• CVE-2017-12598 (8.0 High, published 9 Jul 2026)
• CVE-2019-16249 (published 9 Jul 2026)

CVE-2026-43618 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Affected Packages

References