Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2015-3202

fuse: incorrect filtering of environment variables leading to privilege escalation

Overview

Published
2 Jul 2015
Modified
6 May 2026
Low CVE
0 Registry packages
8 OS packages
4 Linux distributions
Yes Fix available

Description

fusermount in FUSE before 2.9.3-15 does not properly clear the environment before invoking (1) mount or (2) umount as root, which allows local users to write to arbitrary files via a crafted LIBMOUNT_MTAB environment variable that is used by mount's debugging feature.

Source: OX vulnerability database

Severity

7.2 · LOW

CVSS 2.0 base score, scored by redhat.

Access vector
Local
Access complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:N/C:C/I:C/A:C

Weakness: CWE-264

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 11 fixes

Red Hat 1 release · 1 package

wont fix 1
fuse
Red Hat fixes for CVE-2015-3202
ReleasePackageFixed in
7 fuse +2 wont fix

debian 4 releases · 2 packages

fixed 7
ntfs-3g fuse
debian fixes for CVE-2015-3202
ReleasePackageFixed in
11 ntfs-3g 1:2014.2.15AR.3-3
11 fuse 2.9.3-16
12 ntfs-3g 1:2014.2.15AR.3-3
12 fuse 2.9.3-16
13 ntfs-3g 1:2014.2.15AR.3-3
13 fuse 2.9.3-16

1 more row

echo 1 release · 2 packages

fixed 2
ntfs-3g fuse
echo fixes for CVE-2015-3202
ReleasePackageFixed in
ntfs-3g 1:2014.2.15AR.3-3
fuse 2.9.3-16

openSUSE 1 release · 1 package

fixed 1
fuse
openSUSE fixes for CVE-2015-3202
ReleasePackageFixed inAdvisory
Tumbleweed fuse +5 2.9.5-1.6 openSUSE-SU-2024:10378-1

References

Show all 28 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.