# CVE-2025-61141: sqls-server/sqls is vulnerable to command injection in the config command

> Attackers can execute arbitrary commands via the EDITOR environment variable in the sqls-server/sqls tool, requiring an upgrade to mitigate.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-f9f4-5859-29mf, GO-2025-4088

## What is CVE-2025-61141?

CVE-2025-61141 is a high-severity command injection vulnerability in n/a, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

sqls-server/sqls 0.2.28 is vulnerable to command injection in the config command because the openEditor function passes the EDITOR environment variable and config file path to sh -c without sanitization, allowing attackers to execute arbitrary commands.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2025-61141?

3 open source packages ship an affected version, including github.com/sqls-server/sqls.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/sqls-server/sqls` | Go | All versions | None |
| `github.com/sqls-server/sqls` | Go | All versions | None |
| `github.com/sqls-server/sqls` | Go | All versions | None |

## How do I fix CVE-2025-61141?

Upgrade to a fixed version.

## Is CVE-2025-61141 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61141 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61141 and fix it if it is affected.

What it is: CVE-2025-61141 is a high-severity command injection vulnerability in n/a, published on 30 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61141 exists.

Affected packages and fixed versions:
- github.com/sqls-server/sqls (Go): affected all versions; no fix listed
- github.com/sqls-server/sqls (Go): affected all versions; no fix listed
- github.com/sqls-server/sqls (Go): affected all versions; no fix listed

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-2025-61141/ (Markdown: https://insights.sbomify.com/CVE-2025-61141/index.md)
```

## Sources

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

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