# CVE-2026-116205: YesWiki before 4.7.0 Unauthenticated SSRF via [[|URL]] Raw-Inclusion Syntax


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 25 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-fxcp-jrx4-gvc5, GHSA-x9j5-r988-9jcc

## What is CVE-2026-116205?

CVE-2026-116205 is a medium-severity vulnerability in yeswiki, published on 25 Oct 2026. 

### Official description

YesWiki before 4.7.0 contains an unauthenticated server-side request forgery vulnerability that allows remote attackers to fetch arbitrary URLs by supplying [[|URL]] wiki syntax to the render handler. Attackers can pass the syntax in the content parameter of the page render handler to reach internal hosts and ports and read their responses.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-116205 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116205 exists.

Public exploit code:

- YesWiki < 4.7.0 - Unauthenticated Server-Side Request Forgery (nuclei): http/cves/2026/CVE-2026-116205.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116205 is a medium-severity vulnerability in yeswiki, published on 25 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-116205 exists.

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

## Sources

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

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