# CVE-2022-25853: semver-tags is vulnerable to Command Injection via the getGitTagsRemote function

> Attackers can execute arbitrary commands via improper input sanitization in the getGitTagsRemote function of the semver-tags npm package.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2023
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-8h3g-hcwp-6hxq

## What is CVE-2022-25853?

CVE-2022-25853 is a high-severity command injection vulnerability in semver-tags, published on 6 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

All versions of the package semver-tags are vulnerable to Command Injection via the getGitTagsRemote function due to improper input sanitization.

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

## Which versions are affected by CVE-2022-25853?

2 open source packages ship an affected version, including semver-tags. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `semver-tags` | npm | All versions to 0.4.10 | None |
| `semver-tags` | npm | All versions to 0.4.10 | None |

Products: Semver-Tags Project Semver-Tags.

## How do I fix CVE-2022-25853?

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

## Is CVE-2022-25853 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25853 and fix it if it is affected.

What it is: CVE-2022-25853 is a high-severity command injection vulnerability in semver-tags, published on 6 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-25853 exists.

Affected packages and fixed versions:
- semver-tags (npm): affected all versions up to 0.4.10; no fix listed
- semver-tags (npm): affected all versions up to 0.4.10; 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-2022-25853/ (Markdown: https://insights.sbomify.com/CVE-2022-25853/index.md)
```

## Sources

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

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