# CVE-2026-40086: Rembg has a Path Traversal via Custom Model Loading

> Unauthenticated attackers can read arbitrary files from the server filesystem via a crafted model_path parameter in the Rembg HTTP server.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-3wqj-33cg-xc48, PYSEC-2026-2274

## What is CVE-2026-40086?

CVE-2026-40086 is a medium-severity path traversal vulnerability in danielgatis rembg, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rembg is a tool to remove images background. Prior to 2.0.75, a path traversal vulnerability in the rembg HTTP server allows unauthenticated remote attackers to read arbitrary files from the server's filesystem. By sending a crafted request with a malicious model_path parameter, an attacker can force the server to attempt loading any file as an ONNX model, revealing file existence, permissions, and potentially file contents through error messages. This vulnerability is fixed in 2.0.75.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `rembg` | PyPI | All versions | 2.0.75 |
| `rembg` | PyPI | All versions | 2.0.75 |
| `rembg` | PyPI | All versions | 2.0.75 |

Products: Danielgatis Rembg.

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

Upgrade rembg to 2.0.75 or later.

## Is CVE-2026-40086 being exploited?

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

## Other vulnerabilities in danielgatis rembg

- [CVE-2025-25302](https://insights.sbomify.com/CVE-2025-25302/): Rembg CORS misconfiguration (high 8.7)
- [CVE-2025-25301](https://insights.sbomify.com/CVE-2025-25301/): Rembg allows SSRF via /api/remove (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40086 is a medium-severity path traversal vulnerability in danielgatis rembg, published on 10 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-40086 exists.

Affected packages and fixed versions:
- rembg (PyPI): affected all versions; fixed in 2.0.75
- rembg (PyPI): affected all versions; fixed in 2.0.75
- rembg (PyPI): affected all versions; fixed in 2.0.75

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

## Sources

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

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