CVE-2026-48693
Local Symlink Attack in FastNetMon Community Edition
Publication date: 2026-05-26
Last updated on: 2026-05-26
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| fastnetmon | community_edition | to 1.2.9 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-48693 is a local symlink attack vulnerability in FastNetMon Community Edition up to version 1.2.9. The software writes statistics to a predictable and hardcoded file path (/tmp/fastnetmon.dat) without checking for symbolic links or using safe file open flags like O_NOFOLLOW. Additionally, the program sets the file creation mask (umask) to 0, making created files world-writable. Because of these issues, a local attacker can create a symbolic link at the expected file path pointing to an arbitrary file, such as a sensitive system file, and cause FastNetMon to overwrite that file with its data. This can lead to unauthorized file modification and potential privilege escalation.
How can this vulnerability impact me? :
This vulnerability allows a local attacker to overwrite arbitrary files on the system with the permissions of the FastNetMon process user, which is typically root. By exploiting the symlink attack, the attacker can inject malicious content into critical system files, such as cron job files, leading to local privilege escalation. The world-writable permissions on created files further increase the risk by allowing other users to modify these files. Overall, this can compromise system integrity and security.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves a local symlink attack via predictable file paths in /tmp, specifically the file /tmp/fastnetmon.dat being overwritten through symlink exploitation.
To detect if your system is vulnerable or being exploited, you can check for suspicious symlinks pointing from /tmp/fastnetmon.dat to sensitive files.
- Run the command: ls -l /tmp/fastnetmon.dat to see if it is a symlink.
- Use find to locate symlinks in /tmp: find /tmp -type l -ls
- Check for unexpected modifications or world-writable permissions on critical files that could have been overwritten, e.g., ls -l /etc/cron.d/
Additionally, monitoring FastNetMon logs or system audit logs for unusual file operations or permission changes on /tmp/fastnetmon.dat or related files may help detect exploitation attempts.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include preventing symlink attacks on the /tmp directory and restricting file permissions.
- Mount the /tmp directory with the nosymfollow option to prevent following symlinks.
- Enable kernel protections such as fs.protected_symlinks to restrict symlink following by non-owners.
- Manually check and remove any malicious symlinks pointing from /tmp/fastnetmon.dat to sensitive files.
- Restrict permissions on /tmp and related files to prevent world-writable files.
Long-term fixes involve updating FastNetMon to a version that moves the stats file to a private directory, uses O_NOFOLLOW when opening files, and sets a restrictive umask, but as of May 2026 no fix has been released.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows a local attacker to overwrite arbitrary files as root by exploiting insecure handling of temporary files and symlinks. This can lead to unauthorized modification of system files and potential privilege escalation.
Such unauthorized access and modification of system files can compromise the integrity and confidentiality of data, which may violate compliance requirements under standards like GDPR and HIPAA that mandate strict controls over data protection and system security.
Specifically, the ability to inject malicious content (e.g., cron jobs) and escalate privileges could lead to breaches of sensitive personal or health information, undermining regulatory compliance.