# CVE-2026-2265: Replicator 1.0.5 is vulnerable to Remote Code Execution through Insecure Deserialization

> Unauthenticated attackers can achieve remote code execution by sending malicious serialized data to applications using the Replicator npm library.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-2gmp-34j9-fqjm

## What is CVE-2026-2265?

CVE-2026-2265 is a medium-severity unsafe deserialization vulnerability in Replicator, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote code execution (RCE) vulnerability exists in applications that use the Replicator node package manager (npm) version 1.0.5 to deserialize untrusted user input and execute the resulting object.

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

2 open source packages ship an affected version, including replicator.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `replicator` | npm | All versions to 1.0.5 | None |
| `replicator` | npm | All versions to 1.0.5 | None |

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

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

## Is CVE-2026-2265 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2265 is a medium-severity unsafe deserialization vulnerability in Replicator, published on 1 Apr 2026. 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-2026-2265 exists.

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

## Sources

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

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