# CVE-2026-7311: Path traversal in TinyPNG – JPEG, PNG & WebP image compression

> Authenticated attackers can delete arbitrary server files via path traversal, potentially leading to remote code execution.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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:** 2 Jul 2026
- **Updated:** 2 Jul 2026
- **Also known as:** GHSA-p2fp-6329-h7jp

## What is CVE-2026-7311?

CVE-2026-7311 is a high-severity path traversal vulnerability in TinyPNG – JPEG, PNG & WebP image compression, published on 2 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The TinyPNG – JPEG, PNG & WebP image compression plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the delete_converted_image_size function in all versions up to, and including, 3.6.13. This makes it possible for authenticated attackers, with author-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). An attacker can exploit this by injecting an arbitrary server file path into the 'convert.path' field of the 'tiny_compress_images' post meta on an attachment they own, then triggering attachment deletion to invoke the vulnerable code path.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-7311 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7311 is a high-severity path traversal vulnerability in TinyPNG – JPEG, PNG & WebP image compression, published on 2 Jul 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-7311 in the wild and no public exploit code.

Affected product: TinyPNG – JPEG, PNG & WebP image compression. 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-7311/ (Markdown: https://insights.sbomify.com/CVE-2026-7311/index.md)
```

## Sources

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

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