# CVE-2026-78191: WebDyne versions from 2.031 before 3.022 for Perl execute files with .psp anywhere in the name as Perl pages


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-xv5f-qcmp-v8w2

## What is CVE-2026-78191?

CVE-2026-78191 is a critical vulnerability in WebDyne, published on 31 Oct 2026. 

### Official description

WebDyne versions from 2.031 before 3.022 for Perl execute files with .psp anywhere in the name as Perl pages.

WebDyne decides whether to run a requested file as a page by matching its name against WEBDYNE_PSP_EXT_RE, which has no end anchor.

An application that accepts uploads by checking only the final extension lets a remote attacker upload a file such as report.psp.pdf and run its embedded Perl by requesting it.

Weakness: CWE-777 (Regular Expression without Anchors)

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

1 open source package ship an affected version, including WebDyne.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `WebDyne` | cpan | `pkg:cpan/WebDyne` | From 2.031 | 3.022 |

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

Upgrade WebDyne to 3.022 or later.

## Is CVE-2026-78191 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78191 is a critical vulnerability in WebDyne, published on 31 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-78191 in the wild and no public exploit code.

Affected packages and fixed versions:
- WebDyne (cpan): affected from 2.031; fixed in 3.022

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

## Sources

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

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