Skip to main content
CVE-2024-12087VulnerabilityPublished Updated

Red Hat Security Advisory: rsync security update

Affects Red Hat rsyncSource GCVE Database

0
Compare
Authoritative record:CVE-2024-12087· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 3 Nov 2026, 19:18 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.16.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

What to do

AI-suggested

Red Hat has released updated rsync packages that fix the path traversal vulnerability. Users of Red Hat Enterprise Linux 9.2 and related variants should apply the security update as described in Red Hat advisory RHSA-2025:23235. Details on applying the update are available at https://access.redhat.com/articles/11258. No additional mitigation steps are indicated beyond applying the official update.

Description

A path traversal vulnerability (CVE-2024-12087) has been identified in the rsync utility used in Red Hat Enterprise Linux 9.2 and related variants. Rsync is a file synchronization tool that efficiently copies and mirrors files locally or over a network. This vulnerability could allow an attacker to manipulate file paths during synchronization, potentially leading to unauthorized file access or modification. Red Hat has issued a security advisory with an update that addresses this issue.

References

Community reviews

Loading reviews…