# CVE-2026-48696: Memory corruption in n/a

> A buffer overflow in FastNetMon Community Edition allows attackers to execute arbitrary code or cause a denial of service.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2026
- **Updated:** 27 May 2026
- **Also known as:** DEBIAN-CVE-2026-48696, GHSA-vpc6-j22r-6mf9, UBUNTU-CVE-2026-48696

## What is CVE-2026-48696?

CVE-2026-48696 is a medium-severity memory corruption 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 has a buffer overflow, a different vulnerability than CVE-2026-48686 and CVE-2026-48689.

Weakness: CWE-676 (Use of Potentially Dangerous Function), CWE-120 (Buffer Copy without Checking Size of Input)

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

It affects 1 product.


Products: Pavel-Odintsov Fastnetmon.

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

Upgrade to a fixed version.

## Is CVE-2026-48696 being exploited?

There is no known exploitation of CVE-2026-48696 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-48696 and fix it if it is affected.

What it is: CVE-2026-48696 is a medium-severity memory corruption 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-48696 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-48696/ (Markdown: https://insights.sbomify.com/CVE-2026-48696/index.md)
```

## Sources

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

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