# CVE-2026-67578: Missing authorization in FA-50

> An attacker on the internal network can modify configuration settings in the FA-50 marine system due to missing authentication.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/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:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-g4fq-7hvq-hm4q

## What is CVE-2026-67578?

CVE-2026-67578 is a high-severity missing authorization 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 miss authentication for some configuration.
An attacker with access to the vessel's internal network can manipulate the product's settings screen to alter some configuration parameters.

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

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


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

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

## Is CVE-2026-67578 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-67578 is a high-severity missing authorization 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-67578 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-67578/ (Markdown: https://insights.sbomify.com/CVE-2026-67578/index.md)
```

## Sources

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

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