# CVE-2026-112237: Server-Side Request Forgery in extension "Kitodo.Presentation" (dlf)


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-4c29-f9f2-8322

## What is CVE-2026-112237?

CVE-2026-112237 is a medium-severity vulnerability in TYPO3 Extension "Kitodo.Presentation", published on 20 Oct 2026. 

### Official description

The extension provides a public proxy endpoint that fetches a URL on behalf of the visitor. For one HTTP request method, the endpoint does not apply the authorization check that protects the other methods, so the URL it fetches is fully controlled by the requester. An unauthenticated attacker can make the server send requests to arbitrary internal or external hosts. The attacker receives the status code and selected response headers, which allows probing of internal hosts and ports. Response bodies are not disclosed.

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

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


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

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

## Is CVE-2026-112237 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112237 is a medium-severity vulnerability in TYPO3 Extension "Kitodo.Presentation", published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-112237 in the wild and no public exploit code.

Affected product: TYPO3 Extension "Kitodo.Presentation". 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-112237/ (Markdown: https://insights.sbomify.com/CVE-2026-112237/index.md)
```

## Sources

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

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