# CVE-2026-81163: Media Library Importer - Moderately critical - Access bypass - SA-CONTRIB-2026-129


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** DRUPAL-CONTRIB-2026-129, GHSA-pm6w-6qr8-q842

## What is CVE-2026-81163?

CVE-2026-81163 is a medium-severity vulnerability in Drupal Media Library Importer, published on 22 Oct 2026. 

### Official description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Drupal Media Library Importer allows Path Traversal. This issue affects Media Library Importer versions: from 0.0.0 to 2.1.6.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/media_library_importer` | Packagist:https://packages.drupal.org/8 | All versions | 2.1.6 |

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

Upgrade to a fixed version.

## Is CVE-2026-81163 being exploited?

There is no known exploitation of CVE-2026-81163 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81163 is a medium-severity vulnerability in Drupal Media Library Importer, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-81163 in the wild and no public exploit code.

Affected product: Drupal Media Library Importer. 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-81163/ (Markdown: https://insights.sbomify.com/CVE-2026-81163/index.md)
```

## Sources

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

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