# CVE-2025-54314: Command injection in Thor

> An unsafe shell command construction in the Thor library could allow code execution, though the vendor disputes exploitability.

- **Severity:** Low 2.8 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jul 2025
- **Updated:** 10 Aug 2025
- **Also known as:** AZL-65613, AZL-65631, UBUNTU-CVE-2025-54314, openSUSE-SU-2025:15382-1, openSUSE-SU-2026:10366-1

## What is CVE-2025-54314?

CVE-2025-54314 is a low-severity command injection vulnerability in rubyonrails Thor, published on 20 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Thor before 1.4.0 can construct an unsafe shell command from library input. NOTE: this is disputed by the Supplier because "the method that was fixed can only be used with arguments that are controlled by Thor, and there is no way an attacker can take control of those arguments."

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rubygem-thor` | openSUSE:Tumbleweed | All versions | 1.4.0-1.1 |
| `rubygem-thor` | openSUSE:Tumbleweed | All versions | 1.4.0-1.3 |

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

Upgrade to a fixed version.

## Is CVE-2025-54314 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54314 is a low-severity command injection vulnerability in rubyonrails Thor, published on 20 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54314 in the wild and no public exploit code.

Affected product: rubyonrails Thor. 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-2025-54314/ (Markdown: https://insights.sbomify.com/CVE-2025-54314/index.md)
```

## Sources

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

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