{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-48693 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-48693 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-48693 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-48693 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-48693/ (Markdown: https://insights.sbomify.com/CVE-2026-48693/index.md)","id":"CVE-2026-48693","markdown":"https://insights.sbomify.com/CVE-2026-48693/index.md","name":"CVE-2026-48693","record":{"aliases":["DEBIAN-CVE-2026-48693","GHSA-f762-5mrw-32x8","UBUNTU-CVE-2026-48693"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_modify","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Network monitoring software","requires_auth":"low_privilege","summary":"A local attacker can exploit predictable file paths and missing symlink checks to overwrite arbitrary files as root, leading to privilege escalation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fastnetmon","vendor":"pavel-odintsov"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-59","name":"Improper Link Resolution Before File Access"}],"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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Path traversal in n/a","id":"CVE-2026-48693","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Command injection in n/a","id":"CVE-2026-48694"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2026-48692"},"products":["n/a"],"published":"2026-05-26","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2026-48686","kev_date_added":null,"published":"2026-05-26"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2026-48689","kev_date_added":null,"published":"2026-05-26"},{"cvss_score":8.1,"headline":"Command injection in n/a","id":"CVE-2026-48687","kev_date_added":null,"published":"2026-05-26"},{"cvss_score":8.1,"headline":"Missing authorization in n/a","id":"CVE-2026-48692","kev_date_added":null,"published":"2026-05-26"},{"cvss_score":8.1,"headline":"Command injection in n/a","id":"CVE-2026-48694","kev_date_added":null,"published":"2026-05-26"},{"cvss_score":8.1,"headline":"Command injection in n/a","id":"CVE-2026-48695","kev_date_added":null,"published":"2026-05-26"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2026-48688","kev_date_added":null,"published":"2026-05-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-26","vendors":["n/a"]},"summary":"A local attacker can exploit predictable file paths and missing symlink checks to overwrite arbitrary files as root, leading to privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-48693/"}