# CVE-2025-23122: This CVE record has been withdrawn due to a duplicate entry CVE-2025-23165.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 19 May 2025
- **Updated:** 20 May 2025
- **Also known as:** BIT-node-2025-23122, BIT-node-min-2025-23122, GHSA-7q3w-f4rc-vr9m

## What is CVE-2025-23122?

CVE-2025-23122 is a vulnerability in node, published on 19 May 2025. 

### Official description

This CVE record has been withdrawn due to a duplicate entry CVE-2025-23165.

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

2 open source packages ship an affected version, including node and node-min.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node` | Bitnami | All versions | 20.19.2, 22.15.1 |
| `node-min` | Bitnami | All versions | 20.19.2, 22.15.1 |

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

Upgrade node to a fixed version for your release line: 20.19.2 or 22.15.1.

## Is CVE-2025-23122 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-23122 is a vulnerability in node, published on 19 May 2025. 
Exploitation: There is no known exploitation of CVE-2025-23122 in the wild and no public exploit code.

Affected packages and fixed versions:
- node (Bitnami): affected all versions; fixed in 20.19.2, 22.15.1
- node-min (Bitnami): affected all versions; fixed in 20.19.2, 22.15.1

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

## Sources

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

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