# CVE-2026-45452: Unitronics - CWE-134 Use of Externally-Controlled format string

> Attackers can exploit a format string vulnerability in Unitronics UniStream Pro/UniLogic to potentially execute code or cause denial of service.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **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:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-2hvg-pr2c-jr6f

## What is CVE-2026-45452?

CVE-2026-45452 is a high-severity vulnerability in Unitronics UniStream Pro/UniLogic, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Use of Externally-Controlled format string vulnerability in Unitronics Unitronics UniStream Pro/UniLogic.

This issue affects Unitronics UniStream Pro/UniLogic: Unitronics UniStream Pro versions only (B10 / C10) – UniLogic versions prior to 1.41.329.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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


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

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

## Is CVE-2026-45452 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45452 is a high-severity vulnerability in Unitronics UniStream Pro/UniLogic, published on 15 Oct 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-45452 in the wild and no public exploit code.

Affected product: Unitronics UniStream Pro/UniLogic. 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-45452/ (Markdown: https://insights.sbomify.com/CVE-2026-45452/index.md)
```

## Sources

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

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