---
id: "CVE-2026-86019"
kind: "vulnerability"
aliases: ["CVE-2026-86019"]
title: "Part-DB: API base64 upload skips attachment size limit, enabling disk exhaustion"
severity: "medium"
cvss: 5.3
epss: 0.00249
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "part-db", "php", "self-hosted"]
not_affected_if: ["auth-required", "managed-hosting"]
published_at: "2026-10-23T05:17:18+00:00"
first_seen_at: "2026-10-23T21:57:32+00:00"
updated_at: "2026-10-25T04:18:59+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-86019", "first_seen_at": "2026-10-23T21:57:32+00:00"}, {"source": "epss", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-86019", "first_seen_at": "2026-10-24T07:15:51+00:00"}]
---

# Part-DB: API base64 upload skips attachment size limit, enabling disk exhaustion

Part-DB, an open source electronic component inventory system, lets an authenticated API user upload attachments via base64 data without the configured maximum size check applied to browser uploads. An attacker can fill the server's disk with oversized files, causing denial of service.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed Part-DB version, for example in the application's composer.json or release page; versions below `2.13.2` are affected.
- Check whether API access is enabled for users who can create attachments, in the Part-DB permission settings.

## Fix

- Upgrade Part-DB to `2.13.2` or later.
- Until then, restrict API tokens to trusted users and remove attachment-create permission from API roles that do not need it.

## Timeline

- 2026-10-23T21:57:32+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-86019
- 2026-10-24T07:15:51+00:00 epss https://api.first.org/data/v1/epss?cve=CVE-2026-86019

## From the sources

Part-DB is an open source inventory management system for electronic components. Prior to version 2.13.2, Part-DB allows authenticated API users to bypass the configured maximum attachment file size by uploading attachments through the API using base64-encoded file data. The application enforces the configured attachment size limit for normal browser-based file uploads, but the API base64 upload path does not apply the same size validation. As a result, an authenticated user with API access and permission to create attachments can upload files larger than the configured maximum attachment size, potentially exhausting disk space and causing a denial of service. This issue has been patched in version 2.13.2.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_