p PatchFirst

PatchFirst · Latest vulnerabilities

nautilus vulnerabilities

Vulnerabilities published for nautilus in the last 30 days: 1. Listed in the KEV catalogue: 0.

RSS ↗
Filter vulnerabilities
Clear filters

Vulnerabilities: 4

  1. CVE-2026-111802

    Medium · CVSS 6.6EPSS 0.13%No fix published

    Nautilus: nautilus: arbitrary file deletion via trash symlink

    A flaw was found in Nautilus. When a removable drive or disk image is unmounted or ejected, Nautilus prompts the user to empty the trash without verifying whether the trash directory paths are symbolic links. An attacker can exploit this flaw by tricking a user into mounting a crafted storage volume and confirming the prompt to empty the trash, leading to the arbitrary deletion of files accessible to that user.

    Published Updated
  2. CVE-2019-11461

    High · CVSS 7.8EPSS 0.35%Fix available

    CVE-2019-11461

    An issue was discovered in GNOME Nautilus 3.30 prior to 3.30.6 and 3.32 prior to 3.32.1. A compromised thumbnailer may escape the bubblewrap sandbox used to confine thumbnailers by using the TIOCSTI ioctl to push characters into the input buffer of the thumbnailer's controlling terminal, allowing an attacker to escape the sandbox if the thumbnailer has a controlling terminal. This is due to improper filtering of the TIOCSTI ioctl on 64-bit systems, similar to CVE-2019-10063.

    • Update to 3.30.5-2
    Published Updated
  3. CVE-2017-14604

    Medium · CVSS 6.5EPSS 2.47%Fix available

    CVE-2017-14604

    GNOME Nautilus before 3.23.90 allows attackers to spoof a file type by using the .desktop file extension, as demonstrated by an attack in which a .desktop file's Name field ends in .pdf but this file's Exec field launches a malicious "sh -c" command. In other words, Nautilus provides no UI indication that a file actually has the potentially unsafe .desktop extension; instead, the UI only shows the .pdf extension. One (slightly) mitigating factor is that an attack requires the .desktop file to have execute permission. The solution is to ask the user to confirm that the file is supposed to be treated as a .desktop file, and then remember the us

    • Update to 3.25.90-1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →