# CVE-2026-7395: Missing authorization in Asset Suite

> Unauthenticated attackers can access a test servlet to upload configuration files, causing information disclosure and integrity compromise in Hitachi Asset Suite.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-7ch6-fqvg-6pxp

## What is CVE-2026-7395?

CVE-2026-7395 is a high-severity missing authorization vulnerability in Hitachi Energy Asset Suite, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Asset Suite allows unauthenticated users to access HTTPPublishAdapterTestServlet that can be used for configuration file upload, leading to information disclosure and integrity compromise. The HTTPPublishAdapterTestServlet is specifically meant for testing purposes to be used in a non-production environment.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-7395 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7395 and fix it if it is affected.

What it is: CVE-2026-7395 is a high-severity missing authorization vulnerability in Hitachi Energy Asset Suite, published on 29 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-7395 in the wild and no public exploit code.

Affected product: Hitachi Energy Asset Suite. 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-2026-7395/ (Markdown: https://insights.sbomify.com/CVE-2026-7395/index.md)
```

## Sources

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

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