# CVE-2026-16099: Deserialization in Podlove Podcast Publisher

> Authenticated attackers can exploit PHP object injection to delete arbitrary files, potentially leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-q83h-6954-x259

## What is CVE-2026-16099?

CVE-2026-16099 is a high-severity unsafe deserialization vulnerability in eteubert Podlove Podcast Publisher, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Podlove Podcast Publisher plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the create_link_item function in all versions up to, and including, 4.5.3. This makes it possible for authenticated attackers, with contributor-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.php). A viable POP chain exists within the plugin itself via Podlove\ImageCache\GenerationGuard, whose __destruct() method invokes wp_delete_file() with an attacker-controlled file path populated through unserialization.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-16099 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16099 is a high-severity unsafe deserialization vulnerability in eteubert Podlove Podcast Publisher, published on 16 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-16099 in the wild and no public exploit code.

Affected product: eteubert Podlove Podcast Publisher. 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-16099/ (Markdown: https://insights.sbomify.com/CVE-2026-16099/index.md)
```

## Sources

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

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