# CVE-2026-92775: Wiki.js through 2.5.314 Server-Side Request Forgery via Image Prefetch

> Attackers with page editing permissions can exploit Wiki.js Image Prefetch to access internal services and cloud metadata via SSRF.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 16 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-7mqp-q79v-g27v

## What is CVE-2026-92775?

CVE-2026-92775 is a high-severity server-side request forgery vulnerability in requarks Wiki.js, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wiki.js through 2.5.314 contains a server-side request forgery vulnerability in the Image Prefetch renderer that fetches arbitrary URLs without protocol, host, or address validation. Attackers with page editing permissions can inject img elements with the prefetch-candidate class to make the server request internal services and cloud metadata endpoints, with responses returned to the attacker.

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

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


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

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

## Is CVE-2026-92775 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92775 is a high-severity server-side request forgery vulnerability in requarks Wiki.js, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92775 exists.

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

## Sources

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

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