Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach exposed JP1 network service
-
DeliverySend crafted malformed input
-
ExploitTrigger out-of-bounds write (CWE-787)
-
ExecutionCorrupt process memory
-
ImpactDisclose or tamper with data
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Per the vendor CVSS vector (AV:N/AC:L/PR:N/UI:N), no special conditions are indicated - remote, unauthenticated, low-complexity exploitation with no user interaction against affected JP1 components; however, the specific trigger (feature, protocol, or message that reaches the vulnerable code) is not described in the available sources. Limiting factors are version-based: only JP1/Integrated Management 3 - Manager, JP1/Automatic Job Management System 3 - Manager/Agent/Agent Minimal Edition in versions 13-00 before 13-50-31, and JP1/Base 11-00 before 12-50-54 are affected, and exploitation realistically requires the vulnerable JP1 service to be network-reachable by the attacker. No default-configuration dependency is stated either way in the sources. |
| Impact | Signals are mixed and should be weighed carefully. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, score 9.4) describes a remotely reachable, low-complexity, unauthenticated flaw with high confidentiality and integrity impact and low availability impact - severity-wise a top-tier issue, and the vuln.today decision label is 'act_now'. However, the EPSS score is low (0.46%, 39th percentile), indicating no statistical signal of imminent mass exploitation, and the CVE is NOT listed in CISA KEV, so there is no public assertion of active exploitation. No PoC or exploit reference appears in the supplied data. The combination of a very high CVSS/act_now label with a low EPSS and no KEV/PoC suggests the priority is driven by the theoretical severity of a network-reachable out-of-bounds write (CWE-787) rather than by observed in-the-wild activity. Note also a mild internal inconsistency: an out-of-bounds write typically threatens availability, yet the vendor vector rates availability only Low (A:L) while confidentiality and integrity are High - verify the precise impact with Hitachi advisory hitachi-sec-2026-155. Net assessment: patch promptly given the severity and act_now label, but current evidence points to latent/theoretical rather than demonstrated widespread exploitation. |
| Exploit ScenarioDerived | A remote attacker sends specially crafted input over the network to an exposed JP1 management or agent component, triggering an out-of-bounds write in affected memory. Per the CVSS vector this requires no authentication and no user interaction, potentially corrupting memory to disclose or alter sensitive data; the exact trigger is not described in the available sources. No public exploit or PoC reference is provided in the input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
A remote out-of-bounds write in Hitachi's JP1 operations-management suite lets an unauthenticated network attacker corrupt memory in affected JP1 service processes, with the vendor-assigned CVSS 3.1 score of 9.4 reflecting high confidentiality and integrity impact and a partial availability impact (AV:N/AC:L/PR:N/UI:N). Affected are JP1/Integrated Management 3 - Manager, JP1/Automatic Job Management System 3 - Manager, Agent and Agent Minimal Edition from 13-00 before 13-50-31, and JP1/Base from 11-00 before 12-50-54. Hitachi has released fixed versions, no public exploit code or KEV entry was identified at time of analysis, and EPSS is modest at 0.46% (39th percentile), though the vuln.today decision signal is act_now given the unauthenticated network vector and memory-corruption class.
RemediationAI
Vendor-released patch: upgrade JP1/Integrated Management 3 - Manager, JP1/Automatic Job Management System 3 - Manager, Agent and Agent Minimal Edition to 13-50-31 or later, and JP1/Base to 12-50-54 or later, following Hitachi's advisory at https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-155/index.html; the supplied sources identify updating as the vendor remedy and do not document a product-level workaround. Because exploitation requires the vulnerable JP1 service to be network-reachable, as an interim compensating control restrict network access to the affected JP1 manager and agent services to trusted management subnets or jump hosts - the trade-off is that legitimate cross-segment job scheduling and monitoring traffic must be explicitly allow-listed or it will break. Prioritise internet-facing or broadly reachable JP1/Base and manager installations for the upgrade, and treat unexpected crashes or restarts of JP1 service processes as a possible indicator of attempted memory corruption.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 5 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is classified CWE-787 (out-of-bounds write), the same root-cause family as classic buffer overflows: a write operation is performed past the end of an allocated buffer, corrupting adjacent memory. In a long-running management/agent daemon such as those shipped with JP1/Integrated Management 3 and JP1/Automatic Job Management System 3, this class of defect typically manifests as memory corruption that can crash the process (availability impact A:L) or, depending on allocator layout, be steered toward code execution - although the supplied sources do not describe the specific feature, protocol message, or input path that reaches the vulnerable code, so the concrete trigger is not described in the available sources. The CVSS vector indicates the vulnerable code is reachable over the network with no privileges and no user interaction (AV:N/AC:L/PR:N/UI:N), meaning the practical barrier is exposure: the affected JP1 component must be network-reachable by the attacker. CPE data confirms the scope is five Hitachi JP1 product families at the wildcard version level, with EUVD enumerating the concrete ranges on the 13-00 and 11-00 branches.
Know when Jp1 Automatic Job Management System 3 Manager gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
Vendor describes a network-reachable, unauthenticated OOB write with no stated trigger constraints, so AV:N/AC:L/PR:N/UI:N; impacts retained as reported (C:H/I:H/A:L) absent evidence to revise them.
Primary rating from Vendor (Hitachi).
CVSS VectorVendor: Hitachi
Lifecycle Timeline
2DescriptionCVE.org
Out-of-bounds Write 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.
Executive ViewAI
Hitachi's JP1 operations-management suite contains a critical remote memory-corruption vulnerability (CVE-2026-86577) that an unauthenticated network attacker could exploit to compromise affected service processes. This puts organizations relying on JP1 for IT operations and job scheduling at risk of data corruption, service disruption, and potential full system compromise. Leadership should prioritize immediate patching to prevent operational downtime and data integrity issues.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Authentication bypass in Hitachi JP1/Automatic Job Management System 3 - Manager (versions 10-00 up to but not including
A heap-based buffer overflow (CWE-122) in Hitachi JP1/Automatic Job Management System 3 - Manager and 3 - Agent, coverin
Stack-based buffer overflow (CWE-121) in Hitachi JP1/Automatic Job Management System 3 - Manager, - Agent, and - Agent M
Stack-based buffer overflow in Hitachi JP1/AJS3 Manager (versions 10-00 before 13-50-31) could let remote, unauthenticat
Heap-based buffer overflow in Hitachi JP1/Automatic Job Management System 3 - Manager (versions 10-00 through builds pri
Stack-based buffer overflow in Hitachi JP1/Automatic Job Management System 3 - Manager (versions from 10-00 up to but no
Stack-based buffer overflow in Hitachi JP1/Automatic Job Management System 3 Manager, Agent, and Agent Minimal Edition b
Heap-based buffer overflow in Hitachi JP1/Automatic Job Management System 3 Manager, Agent, and Agent Minimal Edition be
Heap-based buffer overflow (CWE-122) in Hitachi JP1/Integrated Management 3 - Manager, JP1/Automatic Job Management Syst
Stack-based buffer overflow in Hitachi JP1/Integrated Management 3 - Manager, JP1/Automatic Job Management System 3 (Man
EUVD-2026-110653
GHSA-c6xv-292f-8jj6
NVD
CVE.org
EPSS
Exploit-DB