# CVE-2026-7512: UTT HiPER 1200GW formUser strcpy buffer overflow

> Remote attackers can exploit a buffer overflow in the UTT HiPER 1200GW router to execute arbitrary code or escalate privileges.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-hcvr-f27c-2hwf

## What is CVE-2026-7512?

CVE-2026-7512 is a high-severity memory corruption vulnerability in UTT HiPER 1200GW, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in UTT HiPER 1200GW up to 2.5.3-1703. The affected element is the function strcpy of the file /goform/formUser. Executing a manipulation can lead to buffer overflow. The attack can be launched remotely. The exploit has been published and may be used.

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-7512?


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

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

## Is CVE-2026-7512 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7512 is a high-severity memory corruption vulnerability in UTT HiPER 1200GW, published on 30 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7512 in the wild and no public exploit code.

Affected product: UTT HiPER 1200GW. 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-7512/ (Markdown: https://insights.sbomify.com/CVE-2026-7512/index.md)
```

## Sources

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

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