# CVE-2026-7381: Plack::Middleware::XSendfile versions through 1.0053 for Perl can allow client-controlled path rewriting

> A malicious client can manipulate headers to read arbitrary files on the server via path rewriting in the deprecated Plack::Middleware::XSendfile library.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Apr 2026
- **Updated:** 30 Apr 2026
- **Also known as:** DEBIAN-CVE-2026-7381, GHSA-j2f5-52cv-9wrh, MGASA-2026-0350, UBUNTU-CVE-2026-7381

## What is CVE-2026-7381?

CVE-2026-7381 is a critical path traversal vulnerability in MIYAGAWA Plack::Middleware::XSendfile, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Plack::Middleware::XSendfile versions through 1.0053 for Perl can allow client-controlled path rewriting.

Plack::Middleware::XSendfile allows the variation setting (sendfile type) to be set by the client via the X-Sendfile-Type header, if it is not considered in the middleware constructor or the Plack environment.

A malicious client can set the X-Sendfile-Type header to "X-Accel-Redirect" to services running behind nginx reverse proxies, and then set the X-Accel-Mapping to map the path to an arbitrary file on the server.

Since 1.0053, Plack::Middleware::XSendfile is deprecated and will be removed from future releases of Plack.

This is similar to CVE-2025-61780 for Rack::Sendfile, although Plack::Middleware::XSendfile has some mitigations that disallow regular expressions to be used in the mapping, and only apply the mapping for the "X-Accel-Redirect" type.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources), CWE-441 (Unintended Proxy or Intermediary), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Miyagawa Plack\.

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

Product is end of life, replace it.

## Is CVE-2026-7381 being exploited?

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

## Other vulnerabilities in MIYAGAWA Plack::Middleware::XSendfile

- [CVE-2014-125112](https://insights.sbomify.com/CVE-2014-125112/): Plack::Middleware::Session::Cookie versions through 0.21 for Perl allows remote code execution (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7381 is a critical path traversal vulnerability in MIYAGAWA Plack::Middleware::XSendfile, published on 29 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-7381 in the wild and no public exploit code.

Affected product: MIYAGAWA Plack::Middleware::XSendfile. 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-7381/ (Markdown: https://insights.sbomify.com/CVE-2026-7381/index.md)
```

## Sources

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

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