# CVE-2026-12192: GALAYOU Y4 Web Server buffer overflow

> A buffer overflow in the GALAYOU Y4 Web Server allows local network attackers to execute arbitrary code or cause denial of service.

- **Severity:** High 8.7 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **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:** 14 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-rm6x-6fv3-45m8

## What is CVE-2026-12192?

CVE-2026-12192 is a high-severity memory corruption vulnerability in GALAYOU Y4, published on 14 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in GALAYOU Y4 1.0.0. Impacted is an unknown function of the component Web Server. This manipulation causes buffer overflow. The attack is only possible within the local network. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-12192 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12192 is a high-severity memory corruption vulnerability in GALAYOU Y4, published on 14 Jun 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-12192 in the wild and no public exploit code.

Affected product: GALAYOU Y4. 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-12192/ (Markdown: https://insights.sbomify.com/CVE-2026-12192/index.md)
```

## Sources

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

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