# CVE-2023-7339: Data collection for dowloading leads into buffer overflow

> A stack-based buffer overflow in Softing Industrial Automation gateways allows attackers to execute arbitrary code or cause denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 27 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-rph6-gq23-6mc9

## What is CVE-2023-7339?

CVE-2023-7339 is a medium-severity memory corruption vulnerability in Softing epGate, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stack-based buffer overflow vulnerability in Softing Industrial Automation GmbH gateways allows overflow buffers.
This issue affects
pnGate: through 1.30
epGate: through 1.30
mbGate: through 1.30
smartLink HW-DP: through 1.30
smartLink HW-PN: through 1.01.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2023-7339?


## How do I fix CVE-2023-7339?

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

## Is CVE-2023-7339 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7339 and fix it if it is affected.

What it is: CVE-2023-7339 is a medium-severity memory corruption vulnerability in Softing epGate, published on 27 Mar 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-2023-7339 in the wild and no public exploit code.

Affected product: Softing epGate. 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-2023-7339/ (Markdown: https://insights.sbomify.com/CVE-2023-7339/index.md)
```

## Sources

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

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