Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-86019— Part-DB: Attachment Size Limit Bypass via API Base64 Upload

Quick assessment

Affected
Part-DB Part-DB-server
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

Part-DB 是一款用于电子元器件的开源库存管理系统。在 2.13.2 版本之前，Part-DB 允许已认证的 API 用户通过 API 上传以 Base64 编码的文件数据，从而绕过系统配置的附件最大文件大小限制。该应用对基于浏览器的常规文件上传强制执行配置的附件大小限制，但 API 的 Base64 上传路径未实施相同的尺寸验证。因此，拥有 API 访问权限且具备创建附件权限的已认证用户可以上传超过配置的最大附件大小的文件，可能导致磁盘空间耗尽并引发拒绝服务（DoS）攻击。该问题已在 2.13.2 版本中修复

CVSS 5.3 · Medium
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-86019

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Part-DB: Attachment Size Limit Bypass via API Base64 Upload
Source: CVE Program / CVE List V5
Vulnerability Description
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
未加控制的资源消耗(资源穷尽)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
Part-DB Part-DB-server < 2.13.2 -

II. Public POCs for CVE-2026-86019

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-86019

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-86019 (1)

Vendor Pages for CVE-2026-86019 (1)

Same Patch Batch · Part-DB · 2026-10-23 · 9 CVEs total

CVE-2026-54630 9.6 CRITICAL Part-DB: Authenticated RCE via .phar attachment upload served from public/media
CVE-2026-86055 8.7 HIGH Part-DB: Password Reset Link Poisoning via Host Header Injection leads to pre-authenticati
CVE-2026-54631 6.3 MEDIUM Part-DB: Hardcoded APP_SECRET enables forged remember-me cookie
CVE-2026-54615 6.0 MEDIUM Part-DB: Stored XSS / HTML injection in activity-log Extra column via unsanitized Collecti
CVE-2026-55600 5.7 MEDIUM Part-DB: Stored HTML injection in BOM validation results via unescaped Part name
CVE-2026-59188 5.4 MEDIUM Part-DB: SVG Sanitization Bypass via Extension Spoofing Leads to Stored XSS in Attachment
CVE-2026-86018 5.3 MEDIUM Part-DB: Authenticated Disk Exhaustion via Unbounded Server-Side Attachment Downloads
CVE-2026-86020 4.6 MEDIUM Part-DB: Spreadsheet Formula Injection in XLSX Part Exports

IV. Related Vulnerabilities

Same product: Part-DB-server
Same vendor: Part-DB
Same weakness: CWE-400

V. Comments for CVE-2026-86019

No comments yet

Leave a comment