# CVE-2026-125729: Plack::Middleware::CSP versions before 0.03 for Perl send the Content Security Policy under the wrong header name, so browsers never enforce it.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-28cm-92qv-48w3

## What is CVE-2026-125729?

CVE-2026-125729 is a vulnerability, published on 10 Nov 2026. 

### Official description

Plack::Middleware::CSP versions before 0.03 for Perl send the Content Security Policy under the wrong header name, so browsers never enforce it.

The call method sets the policy in a response header named "content-security-protocol" instead of "Content-Security-Policy". Browsers ignore that header.

Any cross-site scripting flaw in the wrapped application can run scripts the policy was meant to block.

Weakness: CWE-684 (Incorrect Provision of Specified Functionality)

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


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

No fix has been published for CVE-2026-125729 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-125729 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125729 is a vulnerability, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125729 in the wild and no public exploit code.

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

## Sources

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

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