Skip to main content
VulnerabilityPublished

CVE-2026-37552: mix · Unsafe Deserialization

Affects mixSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High : upgrade to 2.2.18 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.2.18
CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:N/S:U/UI:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade mix-php/mix to 2.2.18.

Affected software

ProductAffectedFixed in
GitHubmix-php/mixpkg:github/mix-php/mixOther threatsAffected
  • <2.2.18
Fixed in
  • 2.2.18

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict access to the localhost TCP port used by the sync-invoke server to trusted users and processes only. Monitor for any unauthorized local access attempts. Do not expose the TCP service beyond localhost. Follow vendor updates closely for any forthcoming patches or official mitigations.

Description

Unsafe deserialization vulnerability in MixPHP Framework 2.x thru 2.2.17. The sync-invoke TCP server (Server.php:87) receives data from a TCP socket, passes it directly to Opis\Closure\unserialize(), then executes the result via call_user_func(). No authentication or signature verification exists on the TCP connection. An attacker with access to the localhost TCP port (server binds 127.0.0.1) can send a crafted serialized PHP closure to achieve arbitrary code execution.

References

Community reviews

Loading reviews…