# CVE-2026-59188: Part-DB: SVG Sanitization Bypass via Extension Spoofing Leads to Stored XSS in Attachment Viewer


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-2vhp-c958-m47j

## What is CVE-2026-59188?

CVE-2026-59188 is a medium-severity vulnerability in Part-DB-server, published on 23 Oct 2026. 

### Official description

Part-DB is an open source inventory management system for electronic components. Prior to version 2.12.3, Part-DB-server sanitizes SVG files based solely on the user-controlled filename extension rather than actual file content type. An authenticated attacker can upload a malicious SVG with JavaScript payload using a non-SVG extension (e.g., .jpg), bypassing sanitization entirely. When any user views the attachment inline, the browser receives Content-Type: image/svg+xml and executes the embedded script in the Part-DB origin. This issue has been patched in version 2.12.3.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2026-59188 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59188 is a medium-severity vulnerability in Part-DB-server, published on 23 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59188 exists.

Affected product: Part-DB-server. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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