# CVE-2026-76131: Hardcoded credentials in VOCALOID6

> Hard-coded credentials in VOCALOID6 allow attackers to impersonate legitimate users and access Yamaha's activation and content servers.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/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:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-j97h-fj62-m9pp

## What is CVE-2026-76131?

CVE-2026-76131 is a medium-severity vulnerability in Yamaha Corporation VOCALOID6, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of hard-coded credentials issue exists in VOCALOID6 , which may allow an attacker to impersonate a legitimate VOCALOID6 Editor and gain access to Yamaha's activation and content servers.

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

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


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

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

## Is CVE-2026-76131 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76131 is a medium-severity vulnerability in Yamaha Corporation VOCALOID6, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-76131 in the wild and no public exploit code.

Affected product: Yamaha Corporation VOCALOID6. 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-76131/ (Markdown: https://insights.sbomify.com/CVE-2026-76131/index.md)
```

## Sources

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

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