CVE-2024-41799
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 1.21 % · percentile 68.93 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
tgstation-server is a production scale tool for BYOND server management. Prior to 6.8.0, 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. This problem is fixed in versions 6.8.0 and above.
Read the publisher's advisorytgstation-server is a production scale tool for BYOND server management. Prior to 6.8.0, 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. This problem is fixed in versions 6.8.0 and above.
Read the publisher's advisorytgstation-server is a production scale tool for BYOND server management. Prior to 6.8.0, 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. This problem is fixed in versions 6.8.0 and above.
Read the publisher's advisory### 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.
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 1.21 % · percentile 68.93 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2024-41799 · 15 Nov 2026 14:45:34 UTC
CVE-2024-41799 · 14 Nov 2026 16:37:01 UTC
CVE-2024-41799 · 13 Nov 2026 19:59:34 UTC
CVE-2024-41799 · 12 Nov 2026 18:18:51 UTC
CVE-2024-41799 · 10 Nov 2026 20:24:10 UTC
CVE-2024-41799 · 09 Nov 2026 21:04:24 UTC
CVE-2024-41799 · 08 Nov 2026 15:12:21 UTC
CVE-2024-41799 · 07 Nov 2026 16:07:52 UTC
CVE-2024-41799 · 06 Nov 2026 19:10:17 UTC
CVE-2024-41799 · 05 Nov 2026 22:49:22 UTC
CVE-2024-41799 · 05 Nov 2026 02:54:06 UTC
CVE-2024-41799 · 03 Nov 2026 16:59:18 UTC
CVE-2024-41799 · 02 Nov 2026 23:59:04 UTC
CVE-2024-41799 · 01 Nov 2026 23:58:58 UTC
CVE-2024-41799 · 01 Nov 2026 03:04:52 UTC
CVE-2024-41799 · 31 Oct 2026 01:52:30 UTC
CVE-2024-41799 · 29 Oct 2026 18:29:26 UTC
CVE-2024-41799 · 28 Oct 2026 19:55:37 UTC
CVE-2024-41799 · 27 Oct 2026 15:46:19 UTC
CVE-2024-41799 · 27 Oct 2026 00:23:05 UTC
CVE-2024-41799 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2024-2316 · Published
euvd · EUVD-2024-2316 · Published
euvd · EUVD-2024-2316 · Published
euvd · EUVD-2024-2316 · Published
euvd · EUVD-2024-2316 · Published
euvd · EUVD-2024-2316 · Published
euvd · EUVD-2024-2316 · Published
euvd · EUVD-2024-2316 · Published
euvd · EUVD-2024-2316 · Published
euvd · EUVD-2024-2316 · Published
nvd · CVE-2024-41799 · Published
osv · GHSA-c3h4-9gc2-f7h4 · Published
cve-program · CVE-2024-41799 · Published