# CVE-2025-65116: Buffer Overflow Vulnerability in JP1/IT Desktop Management 2 and JP1/NETM/DM

> A buffer overflow in Hitachi JP1 desktop management software allows attackers to execute arbitrary code or escalate privileges on Windows systems.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 7 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-qr22-6jgj-x8qh

## What is CVE-2025-65116?

CVE-2025-65116 is a medium-severity memory corruption vulnerability in Hitachi JP1/IT Desktop Management - Manager, published on 7 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Buffer Overflow Vulnerability in JP1/IT Desktop Management 2 - Manager on Windows, JP1/IT Desktop Management 2 - Operations Director on Windows, Job Management Partner 1/IT Desktop Management 2 - Manager on Windows, JP1/IT Desktop Management - Manager on Windows, Job Management Partner 1/IT Desktop Management - Manager on Windows, JP1/NETM/DM Manager on Windows, JP1/NETM/DM Client on Windows, Job Management Partner 1/Software Distribution Manager on Windows, Job Management Partner 1/Software Distribution Client on Windows.This issue affects JP1/IT Desktop Management 2 - Manager: from 13-50 before 13-50-02, from 13-11 before 13-11-04, from 13-10 before 13-10-07, from 13-01 before 13-01-07, from 13-00 before 13-00-05, from 12-60 before 12-60-12, from 10-50 through 12-50-11; JP1/IT Desktop Management 2 - Operations Director: from 13-50 before 13-50-02, from 13-11 before 13-11-04, from 13-10 before 13-10-07, from 13-01 before 13-01-07, from 13-00 before 13-00-05, from 12-60 before 12-60-12, from 10-50 through 12-50-11; Job Management Partner 1/IT Desktop Management 2 - Manager: from 10-50 through 10-50-11; JP1/IT Desktop Management - Manager: from 09-50 through 10-10-16; Job Management Partner 1/IT Desktop Management - Manager: from 09-50 through 10-10-16; JP1/NETM/DM Manager: from 09-00 through 10-20-02; JP1/NETM/DM Client: from 09-00 through 10-20-02; Job Management Partner 1/Software Distribution Manager: from 09-00 through 09-51-13; Job Management Partner 1/Software Distribution Client: from 09-00 through 09-51-13.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-763 (Release of Invalid Pointer or Reference)

## Which versions are affected by CVE-2025-65116?

It affects 5 products.


Products: Hitachi Job Management Partner 1\/It Desktop Management-Manager, Hitachi Jp1\/It Desktop Management 2-Manager, Hitachi Jp1\/It Desktop Management 2-Operations Director, Hitachi Jp1\/Netm\/Dm Client, Hitachi Jp1\/Netm\/Dm Manager.

## How do I fix CVE-2025-65116?

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

## Is CVE-2025-65116 being exploited?

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

## Other vulnerabilities in Hitachi JP1/IT Desktop Management - Manager

- [CVE-2025-65115](https://insights.sbomify.com/CVE-2025-65115/): Remote Code Execution Vulnerability in JP1/IT Desktop Management 2 and JP1/NETM/DM (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-65116 and fix it if it is affected.

What it is: CVE-2025-65116 is a medium-severity memory corruption vulnerability in Hitachi JP1/IT Desktop Management - Manager, published on 7 Apr 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-2025-65116 in the wild and no public exploit code.

Affected product: Hitachi JP1/IT Desktop Management - Manager. 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-2025-65116/ (Markdown: https://insights.sbomify.com/CVE-2025-65116/index.md)
```

## Sources

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

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