CVE-2026-7381
Last modified
CVE-2026-7381 is a critical-severity vulnerability rated 9.1/10 on the CVSS scale. 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.. EPSS estimates a 0.44% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Miyagawa | Plack\ | <= 1.0053 | Middleware\ |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-7381?
How severe is CVE-2026-7381?
How do I fix CVE-2026-7381?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-7375UDS protocol dissector infinite loop in Wireshark 4.6.0 to 4…7.5
- CVE-2026-7376Crash in sharkd 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows de…7.5
- CVE-2026-7377GitLab has remediated an issue in GitLab EE affecting all ve…5.4
- CVE-2026-7378Crash in sharkd 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 allows de…7.5
- CVE-2026-7379Memory leak in sharkd 4.6.0 to 4.6.4 and 4.4.0 to 4.4.14 all…7.5
- CVE-2026-7380Improper neutralization of Script-Related HTML tags in a web…6.1
- CVE-2026-7382Exposure of Sensitive Information to an Unauthorized Actor, …6.5
- CVE-2026-7383Issue summary: A signed integer overflow when sizing the des…8.1
- CVE-2026-7384A vulnerability was detected in ezequiroga mcp-bases 357ca19…7.3
- CVE-2026-7385The Decent Comments WordPress plugin before 3.0.2 does not r…5.8
- CVE-2026-7386A flaw has been found in fatbobman mail-mcp-bridge up to 1.3…7.3
- CVE-2026-7387Mattermost versions 11.6.x <= 11.6.1, 11.5.x <= 11.5.4, 10.1…8.8
Are you affected by CVE-2026-7381?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
