# CVE-2026-65313: Use of hard-coded VNC credentials in the engineering-workstation provisioning

> Hard-coded VNC credentials in provisioning scripts allow adjacent attackers to gain unauthorized access to HIPASE-250 engineering workstations.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-jjwc-g6g3-rhhx

## What is CVE-2026-65313?

CVE-2026-65313 is a high-severity vulnerability in ANDRITZ 250 SCALA, published on 31 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A provisioning script used when installing HIPASE-250 (formerly 250
SCALA) engineering workstations sets a fixed, hard-coded x11vnc
password. Because the same credential is applied to every workstation
provisioned this way, an attacker with adjacent-network access who
knows the password can gain VNC access to affected workstations.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2026-65313 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-65313 is a high-severity vulnerability in ANDRITZ 250 SCALA, published on 31 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65313 in the wild and no public exploit code.

Affected product: ANDRITZ 250 SCALA. 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-65313/ (Markdown: https://insights.sbomify.com/CVE-2026-65313/index.md)
```

## Sources

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

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