# CVE-2025-5150: docarray Web API torch_dataset.py __getitem__ prototype pollution

> Remote attackers can achieve code execution via prototype pollution in the docarray library's Web API component.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 May 2025
- **Updated:** 28 May 2025
- **Also known as:** GHSA-j9wp-865g-rf48, PYSEC-2026-1308

## What is CVE-2025-5150?

CVE-2025-5150 is a medium-severity code injection vulnerability in docarray, published on 25 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in docarray up to 0.40.1. It has been rated as critical. Affected by this issue is the function __getitem__ of the file /docarray/data/torch_dataset.py of the component Web API. The manipulation leads to improperly controlled modification of object prototype attributes ('prototype pollution'). The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

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

3 open source packages ship an affected version, including docarray. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `docarray` | PyPI | All versions to 0.40.1 | None |
| `docarray` | PyPI | All versions to 0.40.1 | None |
| `docarray` | PyPI | All versions to 0.40.1 | None |

Products: Linuxfoundation Docarray.

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

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

## Is CVE-2025-5150 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5150 is a medium-severity code injection vulnerability in docarray, published on 25 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-5150 exists.

Affected packages and fixed versions:
- docarray (PyPI): affected all versions up to 0.40.1; no fix listed
- docarray (PyPI): affected all versions up to 0.40.1; no fix listed
- docarray (PyPI): affected all versions up to 0.40.1; 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-5150/ (Markdown: https://insights.sbomify.com/CVE-2025-5150/index.md)
```

## Sources

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

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