How severe is CVE-2024-41799?

CVE-2024-41799 has a CVSS score of 8.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2024-41799?

CVE-2024-41799 affects the following packages: Tgstation.Server.Api (NuGet), Tgstation.Server.Host (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2024-41799?

Update Tgstation.Server.Api to 6.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41799 is resolved across your whole dependency graph.

How do I detect CVE-2024-41799 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Tgstation.Server.Api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-41799 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2024-41799 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-41799 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-41799?

CVE-2024-41799 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 69th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-41799?

CVE-2024-41799 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-41799 published, and has it been updated?

CVE-2024-41799 was published on July 29, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET

.NET NuGet

Not in CISA KEV

HIGH severity

CVE-2024-41799 — Tgstation.Server.Api

HIGHFix: tgstation/tgstation-server@374852f

CVE-2024-41799 is a high-severity (CVSS 8.4) Path Traversal vulnerability in Tgstation.Server.Api. A fix is available for Tgstation.Server.Api — see the affected versions and patch details below.

tgstation-server's DreamMaker environment files outside the deployment directory can be compiled and ran by insufficiently permissioned users

Also known asGHSA-c3h4-9gc2-f7h4

Published

Jul 29, 2024

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-41799.

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

.NETTgstation.Server.Api.NETTgstation.Server.Host

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Impact

What kind of vulnerability is it? Who is impacted?

Low permission users using the "Set .dme Path" privilege could potentially set malicious .dme files existing on the host machine to be compiled and executed.

These .dme files could be uploaded via tgstation-server (requiring a separate, isolated privilege) or some other means.

A server configured to execute in BYOND's trusted security level (requiring a third separate, isolated privilege OR being set by another user) could lead to this escalating into remote code execution via BYOND's shell() proc.

The ability to execute this kind of attack is a known side effect of having privileged TGS users, but normally requires multiple privileges with known weaknesses. This vector is not intentional as it does not require control over the where deployment code is sourced from and may not require remote write access to an instance's Configuration directory.

Patches

Has the problem been patched? What versions should users upgrade to?

This problem is patched by pull request #1835 and fixed in versions 6.8.0 and above.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

Do not give un-trusted users the Deployment permission to set a .dme path on instances.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Tgstation.Server.Api`	≥ 4.0.0&&< 6.8.0	6.8.0`dotnet add package Tgstation.Server.Api --version 6.8.0`
.NETNuGet	`Tgstation.Server.Host`	≥ 4.0.0&&< 6.8.0	6.8.0`dotnet add package Tgstation.Server.Host --version 6.8.0`

Affected Products

1 product · 1 configurations

Application

tgstation-servertgstation13

≥ 4.0.0 && < 6.8.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Tgstation.Server.Api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Tgstation.Server.Api to 6.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-41799 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ Low permission users using the "Set .dme Path" privilege could potentially set malicious .dme files existing on the host machine to be compiled and executed. These .dme files could be uploaded via tgstation-server (requiring a separate, isolated privilege) or some other means. A server configured to execute in BYOND's trusted security level (requiring a third separate, isolated privilege OR being set by another user) could lead to this escalating into remote code execution via BYOND's shell() proc. The ability to execute this