JP1/Integrated Management 3 - Manager: Heap-based Buffer Overflow
CVE-2026-86576 is a critical-severity heap-based buffer overflow vulnerability in JP1/Integrated Management 3 - Manager from Hitachi, with a CVSS 3.1 base score of 9.4 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 13-50-31 as the first without the flaw, so updating JP1/Integrated Management 3 - Manager to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.45% chance of exploitation within 30 days, which is low compared with other CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update JP1/Integrated Management 3 - Manager to 13-50-31 or a later version.
- Update JP1/Automatic Job Management System 3 - Manager to 13-50-31 or a later version.
- Update JP1/Automatic Job Management System 3 - Agent to 13-50-31 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Hitachi | JP1/Integrated Management 3 - Manager | 13-00 up to, but not including, 13-50-31 | 13-50-31 |
| Hitachi | JP1/Automatic Job Management System 3 - Manager | 13-00 up to, but not including, 13-50-31 | 13-50-31 |
| Hitachi | JP1/Automatic Job Management System 3 - Agent | 13-00 up to, but not including, 13-50-31 | 13-50-31 |
| Hitachi | JP1/Automatic Job Management System 3 - Agent Minimal Edition | 13-00 up to, but not including, 13-50-31 | 13-50-31 |
| Hitachi | JP1/Base | 11-00 up to, but not including, 12-50-54 | 12-50-54 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L. Scored by CNA (hitachi.co.jp).
Official description
Heap-based Buffer Overflow Vulnerability in JP1 Products. This issue affects JP1/Integrated Management 3 - Manager: from 13-00 before 13-50-31; JP1/Automatic Job Management System 3 - Manager: from 13-00 before 13-50-31; JP1/Automatic Job Management System 3 - Agent: from 13-00 before 13-50-31; JP1/Automatic Job Management System 3 - Agent Minimal Edition: from 13-00 before 13-50-31; JP1/Base: from 11-00 before 12-50-54.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Heap-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the heap.
How developers prevent this class of flaw
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in JP1/Integrated Management 3 - Manager
- 9.4 Critical severity
- 9.4 Critical severity
Recent Heap-based Buffer Overflow vulnerabilities
- 8.8 High severity
- 9.3 Critical severity
- 7.7 High severity
- 9.2 Critical severity
- 9.2 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.