# CVE-2026-48693: Path traversal in n/a

> A local attacker can exploit predictable file paths and missing symlink checks to overwrite arbitrary files as root, leading to privilege escalation.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 26 May 2026
- **Also known as:** DEBIAN-CVE-2026-48693, GHSA-f762-5mrw-32x8, UBUNTU-CVE-2026-48693

## What is CVE-2026-48693?

CVE-2026-48693 is a medium-severity path traversal vulnerability in n/a, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

FastNetMon Community Edition through 1.2.9 is vulnerable to a local symlink attack via predictable file paths in /tmp. The statistics file path defaults to '/tmp/fastnetmon.dat' (src/fastnetmon.cpp line 159). The print_screen_contents_into_file() function (src/fastnetmon_logic.cpp line 2186) opens this path with std::ios::trunc without checking for symlinks or using O_NOFOLLOW. Additionally, the chmod() call on line 2190 always operates on cli_stats_file_path regardless of which file_path parameter was passed (a bug that applies wrong permissions), and the umask is set to 0 during daemonization (src/fastnetmon.cpp line 1821), making all created files world-writable. A local attacker can exploit this to overwrite arbitrary files as the FastNetMon process user (typically root).

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2026-48693?

It affects 1 product.


Products: Pavel-Odintsov Fastnetmon.

## How do I fix CVE-2026-48693?

No fix has been published for CVE-2026-48693 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48693 being exploited?

There is no known exploitation of CVE-2026-48693 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2026-48686](https://insights.sbomify.com/CVE-2026-48686/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-48689](https://insights.sbomify.com/CVE-2026-48689/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-48687](https://insights.sbomify.com/CVE-2026-48687/): Command injection in n/a (high 8.1)
- [CVE-2026-48692](https://insights.sbomify.com/CVE-2026-48692/): Missing authorization in n/a (high 8.1)
- [CVE-2026-48694](https://insights.sbomify.com/CVE-2026-48694/): Command injection in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48693 and fix it if it is affected.

What it is: CVE-2026-48693 is a medium-severity path traversal vulnerability in n/a, published on 26 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48693 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48693/ (Markdown: https://insights.sbomify.com/CVE-2026-48693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48693
- OSV: https://osv.dev/vulnerability/CVE-2026-48693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48693/
Summaries are generated and may contain mistakes; the official description above is the record.