Is CVE-2026-86019 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-86019 being exploited in the wild.

How severe is CVE-2026-86019?

Informational severity, published 23 October 2026.

Is there a fix for CVE-2026-86019?

Yes: fixed in 2.13.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-86019 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-86019?

Check whether you run Part-DB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-86019: Part-DB attachment size limit bypass via API base64 upload

CVE-2026-86019 · Severity: info · Published 2026-10-23

Part-DB is an open source inventory management system for electronic components. An authenticated API user can bypass the configured maximum attachment file size by uploading files encoded as base64 through the API, while normal browser uploads are restricted. An attacker with API access could upload large files to exhaust disk space and cause the system to become unavailable.

Technologies: Part-DB. Vendors: Part-DB.

Quick answers

Is CVE-2026-86019 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-86019 being exploited in the wild.
How severe is CVE-2026-86019?: Informational severity, published 23 October 2026.
Which products and versions are affected?: Part-DB prior to 2.13.2.
Is there a fix for CVE-2026-86019?: Yes: fixed in 2.13.2. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-86019 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-86019?: Check whether you run Part-DB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 2.13.2

Technical details

The vulnerability exists in the API attachment upload flow: when attachments are created via API with base64-encoded data, the AttachmentSubmitHandler processes the data without enforcing the configured MAX_ATTACHMENT_FILE_SIZE limit. Normal browser-based uploads are validated at the Symfony form layer, but the API base64 path bypasses this check. An authenticated API user with attachment creation permissions can submit oversized base64-encoded files, which the application will decode and store, potentially causing denial of service.

Affected products

Part-DB Part-DB prior to 2.13.2

Timeline

2026-07-19: disclosed
2026-07-16: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.