txAdmin 8.1.2 Security Release
Update FXServer to 37850 and Cfx Server to 170
Cfx released txAdmin 8.1.2 on October 23, 2026 as a security update. It addresses a recently disclosed vulnerability in one of txAdmin's upstream dependencies. Cfx say they are not aware of any active exploitation affecting the Cfx platform or txAdmin, and describe the release as a precautionary measure - but they strongly recommend updating to the latest server versions as soon as practical.
The official advisory is GHSA-9v8h-qqgm-4m35 - read the GitHub security advisory. The txAdmin 8.1.2 release is also on GitHub: txAdmin v8.1.2.
🛡️ What The Release Addresses
The advisory is for a critical vulnerability in an upstream dependency, tracked as CVE-2026-111497 / GHSA-9v8h-qqgm-4m35. It is a Node.js Brotli decompression issue with a CVSS score of 9.2 - network attack vector, low complexity, no privileges and no user interaction required.
The txAdmin 8.1.2 release notes describe the fix as rejecting compressed request bodies in the core web server. That is a server-side mitigation: the panel no longer accepts the request shape that could trigger the upstream flaw. You do not need to change your txAdmin configuration to benefit - you need to run the fixed build.
📦 Required Versions
- FXServer (FiveM for GTAV Legacy and RedM): 37850
- Cfx Server (FiveM for GTAV Enhanced): 170
- txAdmin: 8.1.2
Download updated server artifacts from the official Cfx documentation: FiveM / RedM server downloads.
If you use the txAdmin build bundled with FXServer or Cfx Server, updating the artifact gets you the fixed version. If you run txAdmin separately, update txAdmin itself to 8.1.2 and confirm the version in the panel after restarting.
✅ Update Checklist
- Inventory every server you run. Legacy FiveM, RedM and GTAV Enhanced are separate builds, and each needs the corresponding update.
- Update FXServer Legacy and RedM to 37850 or newer.
- Update Cfx Server for GTAV Enhanced to 170 or newer.
- Confirm txAdmin reports 8.1.2 after the restart. An updated artifact with an old separately-managed txAdmin is not the same thing.
- Restart during a quiet window. A security update is not worth dropping a populated server mid-event, but it should not wait for the next monthly maintenance either.
- Check the server console and txAdmin logs after restarting for startup errors or version warnings.
- Back up before updating. Artifact updates can interact with resources, framework versions and custom txAdmin configuration. Keep a known-good build and a current backup.
- Review panel exposure. txAdmin should not be open to the public internet without a reason. Restrict access where possible, use a strong password and enable two-factor authentication if your setup supports it.
- Do not wait for active exploitation reports. The advisory is critical and the fix is available now. "No known exploitation" is a statement about the present, not a guarantee about next week.
🧩 Why This Is A Server-Owner Release, Not A Client One
This is not a gameplay patch. Players do not need to do anything, and there is no new client feature to announce. The change is in the management layer: txAdmin's web server and the dependency that handles compressed request bodies.
That makes it easy to defer, which is exactly why it is worth scheduling. A panel vulnerability is not visible in-game - there is no crash, no error message and no player complaint. The only signal is the version number. If you manage multiple communities or a hosting setup with several servers, check them all rather than assuming the artifact update covered every panel.
🖥️ What This Means For Your Community
- No player action required. This is an admin-side security update; clients do not need a new build for it.
- Schedule a short restart. Treat it like maintenance, not an emergency outage. Pick a low-population window and announce it.
- Verify the panel version after updating. If your host manages txAdmin for you, ask them to confirm 8.1.2 or the artifact versions above.
- Keep the panel off the public internet where possible. Security updates reduce risk; they do not make an exposed admin panel a good idea.
- Record what you updated. With separate Legacy, RedM and Enhanced servers, a simple checklist prevents one build being missed for months.
Running a FiveM or RedM community? NolimitHost FiveM server hosting keeps your server on current artifacts with fast high-clock CPUs, NVMe storage, DDoS protection and automated backups - and RedM hosting is available too.
Conclusion
txAdmin 8.1.2 is a security release addressing a critical upstream dependency vulnerability (GHSA-9v8h-qqgm-4m35 / CVE-2026-111497) by rejecting compressed request bodies. Cfx are not aware of active exploitation affecting the platform or txAdmin, but recommend updating promptly. Update FXServer to 37850 for FiveM Legacy and RedM, Cfx Server to 170 for GTAV Enhanced, and confirm txAdmin 8.1.2 is running.
Read the official advisory: GHSA-9v8h-qqgm-4m35. For the month's other platform changes, see our server metadata Portal update and Steam authentication update breakdowns.