# CVE-2026-40041: Pachno 1.0.6 Cross-Site Request Forgery via State-Changing Endpoints

> Attackers can force authenticated users to perform actions like file uploads or role changes via CSRF in Pachno.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:L/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Apr 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-7mjm-hv2p-32c3

## What is CVE-2026-40041?

CVE-2026-40041 is a medium-severity vulnerability in Pachno, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Pachno 1.0.6 contains a cross-site request forgery vulnerability that allows attackers to perform arbitrary actions in authenticated user context by exploiting missing CSRF protections on state-changing endpoints. Attackers can craft malicious requests targeting login, registration, file upload, milestone editing, and administrative functions to force logout, create accounts, modify roles, inject comments, or upload files when authenticated users visit attacker-controlled websites.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-40041 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40041 is a medium-severity vulnerability in Pachno, published on 13 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-40041 in the wild and no public exploit code.

Affected product: Pachno. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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