Quick answers
- Is CVE-2026-78191 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78191 being exploited in the wild.
- How severe is CVE-2026-78191?
- Informational severity, published 31 October 2026.
- Which products and versions are affected?
- ASPEER WebDyne 2.031 to before 3.022.
- Is there a fix for CVE-2026-78191?
- Yes: fixed in WebDyne 3.022. Until then: Restrict upload functionality to reject files containing .psp anywhere in the filename, not just at the end. Additionally, configure the web server to prevent execution of Perl scripts outside designated directories. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78191 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-78191?
- Check whether you run ASPEER WebDyne at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: WebDyne 3.022
Restrict upload functionality to reject files containing .psp anywhere in the filename, not just at the end. Additionally, configure the web server to prevent execution of Perl scripts outside designated directories.
Technical details
The WEBDYNE_PSP_EXT_RE regular expression used to identify executable PSP pages lacks an end anchor, causing it to match .psp anywhere in the filename rather than only at the end. An attacker can bypass file-upload filters that validate only the final extension by uploading a file with .psp embedded in the middle (e.g., "report.psp.pdf"), and then request the file to have it executed as a Perl page. This requires an application using WebDyne with upload functionality that validates only the trailing extension.
Affected products
- ASPEER WebDyne 2.031 to before 3.022
Timeline
- 2026-10-31: disclosed
- 2026-08-25: patched