# CVE-2026-59769: Hardcoded credentials in FA-50

> An attacker with internal network access can use hard-coded credentials to alter the identification number on the FA-50 marine transponder.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/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:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-g7r6-9fmr-hmhc

## What is CVE-2026-59769?

CVE-2026-59769 is a high-severity vulnerability in FURUNO ELECTRIC CO., LTD. FA-50, published on 25 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

FA-50 all versions contain hard-coded credentials.
An attacker, who knows the credentials and has access to the vessel's internal network, can operate the settings screen using that credentials to alter the identification number.

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

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


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

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

## Is CVE-2026-59769 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59769 is a high-severity vulnerability in FURUNO ELECTRIC CO., LTD. FA-50, published on 25 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-59769 in the wild and no public exploit code.

Affected product: FURUNO ELECTRIC CO., LTD. FA-50. 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-59769/ (Markdown: https://insights.sbomify.com/CVE-2026-59769/index.md)
```

## Sources

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

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