# CVE-2026-55239: Tianji: SQL Injection via unsanitized timezone parameter in analytics queries

> An authenticated user can execute arbitrary SQL via the timezone parameter, potentially exposing or modifying sensitive tenant data and credentials.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-v9jm-vvrj-53c4

## What is CVE-2026-55239?

CVE-2026-55239 is a high-severity SQL injection vulnerability in msgbyte tianji, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-55239?


## How do I fix CVE-2026-55239?

No fix has been published for CVE-2026-55239 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-55239 being exploited?

There is no known exploitation of CVE-2026-55239 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55239 and fix it if it is affected.

What it is: CVE-2026-55239 is a high-severity SQL injection vulnerability in msgbyte tianji, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55239 in the wild and no public exploit code.

Affected product: msgbyte tianji. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55239/ (Markdown: https://insights.sbomify.com/CVE-2026-55239/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55239
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55239
- OSV: https://osv.dev/vulnerability/CVE-2026-55239

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55239/
Summaries are generated and may contain mistakes; the official description above is the record.