# CVE-2026-116822: YesWiki before 4.7.0 Template Traversal via BazarListeAction template Parameter


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-56wp-34hq-q74f, GHSA-qfv2-x8g4-qg27

## What is CVE-2026-116822?

CVE-2026-116822 is a medium-severity vulnerability in yeswiki, published on 26 Oct 2026. 

### Official description

YesWiki before 4.7.0 contains a path traversal vulnerability in BazarListeAction that allows unauthenticated attackers to select arbitrary templates within the @bazar Twig namespace via the template GET parameter. Attackers can append crafted template values to pages containing the bazarliste action to force unintended layouts, causing page defacement for visitors following the crafted link.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-116822 being exploited?

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

## Fix prompt for AI coding agents

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

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

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

## Sources

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

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