CVE-2026-55239: Tianji: SQL Injection via unsanitized timezone parameter in analytics queries
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Tianji is an open source analytics, uptime monitoring, and server status platform. Prior to 1.31.29, the getDateQuery() function in src/server/utils/prisma.ts constructs raw SQL through Prisma.sql() by interpolating the timezone request value without parameter binding. The timezone value can reach affected analytics queries through request data or the timezone HTTP header, and workspaceProcedure permits any authenticated workspace member, including a read-only viewer, to reach those queries. An attacker can execute arbitrary SQL against the shared PostgreSQL database, which can disclose or modify credentials, API keys, and tenant data or make the service unavailable. This issue is fixed in version 1.31.29.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-10-15).
Weakness: CWE-89: Improper Neutralization of Special Elements used in an SQL Command (‘SQL Injection’)
How it can be exploited
Exploitable over the network with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Also known as: EUVD-2026-102244
VEDAS cluster: VEDAS:DOLPHINDELIVERY
Exploit Observer links 3 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (3)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-55239.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-55239.rules
- Code repository: https://raw.githubusercontent.com/ARPSyndicate/vedas-signatures/main/suricata/2026/CVE-2026-55239.rules
Vulnerability databases and vendor advisories (2)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-102244
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-55239
2 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.986
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| msgbyte tianji | version < 1.31.29 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-55239 Tianji - Timezone SQL Injection. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-55239 Tianji - Timezone SQL Injection"; flow:established,to_server; http.header; content:"timezone"; nocase; fast_pattern; pcre:"/timezone[^\r\n]*(?:'|%27)[^\r\n]*(?:select|union|sleep|pg_sleep|insert|update|delete)/i"; classtype:web-application-attack; reference:cve,CVE-2026-55239; reference:url,https://www.exploit.observer/?keyword=CVE-2026-55239&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=tianji&match=exact; sid:1084400; rev:1;)
CVE-2026-55239.rules on GitHub
References
Other references
- https://github.com/msgbyte/tianji/security/advisories/GHSA-v9jm-vvrj-53c4 (x_refsource_CONFIRM)
- https://github.com/msgbyte/tianji/commit/132ff67907df897d222829ea8ad1a018ff74df48 (x_refsource_MISC)
- https://github.com/msgbyte/tianji/releases/tag/v1.31.29 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.