# CVE-2023-54338: Tftpd32_SE 4.60 - 'Tftpd32_svc' Unquoted Service Path

> Local attackers can execute arbitrary code with system privileges by exploiting an unquoted service path in Tftpd32 SE.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-xgq4-gwmr-jvcm

## What is CVE-2023-54338?

CVE-2023-54338 is a high-severity vulnerability in Pjo2 Tftpd32_SE, published on 13 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Tftpd32 SE 4.60 contains an unquoted service path vulnerability that allows local attackers to potentially execute arbitrary code with elevated privileges. Attackers can exploit the unquoted path in the service configuration to inject malicious executables that will be run with system-level permissions.

Weakness: CWE-428 (Unquoted Search Path or Element)

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


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

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

## Is CVE-2023-54338 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-54338 is a high-severity vulnerability in Pjo2 Tftpd32_SE, published on 13 Jan 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-2023-54338 in the wild and no public exploit code.

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

## Sources

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

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