# CVE-2026-78188: WebDyne versions from 2.014 before 3.022 for Perl issue session cookies without the Secure, HttpOnly and SameSite attributes.


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-939g-4f3p-xc2m

## What is CVE-2026-78188?

CVE-2026-78188 is a medium-severity vulnerability in WebDyne, published on 31 Oct 2026. 

### Official description

WebDyne versions from 2.014 before 3.022 for Perl issue session cookies without the Secure, HttpOnly and SameSite attributes.

WebDyne::Session sets its session cookie with only a name, value and path.

Browsers then send the session ID over plain HTTP and with cross-site requests, and expose it to page scripts. A network attacker or an injected script can steal the session, and another site can make requests that carry it.

Weakness: CWE-614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute), CWE-1275 (Sensitive Cookie with Improper SameSite Attribute), CWE-1004 (Sensitive Cookie Without 'HttpOnly' Flag)

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

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


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

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

Upgrade WebDyne to 3.022 or later.

## Is CVE-2026-78188 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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