# CVE-2026-97225: DbGate JSON Runner runners.js code injection

> Remote attackers can execute arbitrary code in DbGate by manipulating JSON Runner arguments, requiring an upgrade to the latest version.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **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:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-wfmr-v458-6g7f

## What is CVE-2026-97225?

CVE-2026-97225 is a medium-severity code injection vulnerability in DbGate, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in DbGate up to 7.2.5-beta.5. This affects an unknown function of the file packages/api/src/controllers/runners.js of the component JSON Runner. Executing a manipulation of the argument comment.text/script.schedule can lead to code injection. The attack may be performed from remote. Upgrading to version 7.2.5-beta.6 mitigates this issue. This patch is called 70e7b6b58e464d7a015ba16e8d7574b420ee4877. Upgrading the affected component is advised. This issue is distinct from CVE-2026-47668.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-97225 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-97225 is a medium-severity code injection vulnerability in DbGate, published on 24 Sep 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-97225 in the wild and no public exploit code.

Affected product: DbGate. 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-97225/ (Markdown: https://insights.sbomify.com/CVE-2026-97225/index.md)
```

## Sources

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

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