CVE-2026-71374
Deserialization RCE in Hitachi Cosminexus Component Container
Is CVE-2026-71374 being exploited?
Not confirmed. CVE-2026-71374 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-71374?
CVE-2026-71374 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71374?
Yes. A fix has been recorded for CVE-2026-71374. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-71374 affect?
CVE-2026-71374 affects Hitachi Cosminexus Component Container (multiple versions across 09-00 through 11-70 series; see vendor advisory). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71374?
Apply vendor fixed versions immediately; isolate affected hosts and monitor logs/IDS.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via deserialization of untrusted data, enabling arbitrary code execution, system takeover, and privilege escalation.
Immediate action required
- affected>= 11-70-01 and < 11-70-03
- affected>= 11-60 and < 11-60-03
- affected>= 11-50 and <= 11-50-03
- affected>= 11-40 and <= 11-40-03
- affected>= 11-30 and <= 11-30-08
- affected>= 11-20 and < 11-20-10
- affected>= 11-10 and <= 11-10-11
- affected>= 11-00 and < 11-00-13
- affected>= 09-87 and < 09-87-10
- affected>= 09-80 and < 09-80-05
- affected>= 09-70 and < 09-70-28
- affected>= 09-50 and <= 09-50-22
- affected>= 09-00 and <= 09-00-18
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.