# CVE-2026-42471: Deserialization in n/a

> An attacker controlling the server response can achieve remote code execution on the client via unsafe deserialization in the MixPHP Framework sync-invoke client.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2026
- **Updated:** 1 May 2026
- **Also known as:** GHSA-jc3r-732w-jg7c

## What is CVE-2026-42471?

CVE-2026-42471 is a high-severity unsafe deserialization vulnerability in n/a, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Unsafe deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17. The sync-invoke client (Connection.php:76) calls unserialize() on data received from the server response, enabling client-side RCE if connecting to a malicious server.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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


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

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

## Is CVE-2026-42471 being exploited?

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

Public exploit code:

- MixPHP Framework 2.2.17 - Unsafe Deserialization Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42471 is a high-severity unsafe deserialization vulnerability in n/a, published on 1 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-42471 in the wild and no public exploit code.

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

## Sources

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

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