# CVE-2026-111234: SimplePie through 1.9.0 Local File Read via file:// Redirect

> Attackers can read server files via file:// URLs in feed redirects, exposing sensitive data to malicious feed servers.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-9fwh-fc64-58p8

## What is CVE-2026-111234?

CVE-2026-111234 is a high-severity path traversal vulnerability in simplepie, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SimplePie through 1.9.0 contains a local file read vulnerability that allows malicious feed servers to read server files by supplying file:// URLs in redirects or autodiscovery links. Attackers can return a Location header or feed link pointing to a file:// path, causing file_get_contents() to read files accessible to the web server process.

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

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


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

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

## Is CVE-2026-111234 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111234 is a high-severity path traversal vulnerability in simplepie, published on 15 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111234 exists.

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

## Sources

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

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