# CVE-2026-78192: WebDyne versions from 2.022 before 3.022 for Perl disclose application source to unauthenticated clients via the viewer in the default index page.


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-hf35-9v4j-23x2

## What is CVE-2026-78192?

CVE-2026-78192 is a high-severity vulnerability in WebDyne, published on 31 Oct 2026. 

### Official description

WebDyne versions from 2.022 before 3.022 for Perl disclose application source to unauthenticated clients via the viewer in the default index page.

WebDyne's wrapper scripts, such as webdyne.psgi, enable the built-in index page by default. Its source viewer returns files under the document root named in the source parameter of an HTMX request, including .psp, .pm and .pl files.

A remote attacker can read the application's Perl code, including the __PERL__ blocks of .psp pages and any credentials they hold.

Weakness: CWE-540 (Inclusion of Sensitive Information in Source Code), CWE-1188 (Initialization of a Resource with an Insecure Default)

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

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


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

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

Upgrade WebDyne to 3.022 or later.

## Is CVE-2026-78192 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- WebDyne (cpan): affected from 2.022; 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-78192/ (Markdown: https://insights.sbomify.com/CVE-2026-78192/index.md)
```

## Sources

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

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