Vulnerability in php-zumba-json-serializer (DEBIAN-CVE-2026-27206)
Summary
Vulnerability in php-zumba-json-serializer (DEBIAN-CVE-2026-27206). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.2.4-1 or later.
Original description
The description as published by the source.
Zumba Json Serializer is a library to serialize PHP variables in JSON format. In versions 3.2.2 and below, the library allows deserialization of PHP objects from JSON using a special @type field. The deserializer instantiates any class specified in the @type field without restriction. When processing untrusted JSON input, this behavior may allow an attacker to instantiate arbitrary classes available in the application. If a vulnerable application passes attacker-controlled JSON into JsonSerializer::unserialize() and contains classes with dangerous magic methods (such as __wakeup() or __destruct()), this may lead to PHP Object Injection and potentially Remote Code Execution (RCE), depending on available gadget chains in the application or its dependencies. This behavior is similar in risk profile to PHP's native unserialize() when used without the allowed_classes restriction. Applications are impacted only if untrusted or attacker-controlled JSON is passed into JsonSerializer::unserialize() and the application or its dependencies contain classes that can be leveraged as a gadget chain. This issue has been fixed in version 3.2.3. If an immediate upgrade isn't feasible, mitigate the vulnerability by never deserializing untrusted JSON with JsonSerializer::unserialize(), validating and sanitizing all JSON input before deserialization, and disabling @type-based object instantiation wherever possible.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as DEBIAN-CVE-2026-27206 has been found in php-zumba-json-serializer.
Successful exploitation can lead to full system takeover.
What to do: upgrade php-zumba-json-serializer to 3.2.4-1 or later.
If unsure, ask your IT team or search "php-zumba-json-serializer DEBIAN-CVE-2026-27206" on the vendor's site.
DEBIAN-CVE-2026-27206 (php-zumba-json-serializer)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.2.4-1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in php-zumba-json-serializer.
Check the vendor advisory for the affected versions of php-zumba-json-serializer.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 3.2.4-1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'php-zumba-json-serializer' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'php-zumba-json-serializer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
php-zumba-json-serializerを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade php-zumba-json-serializer to 3.2.4-1ステージング環境で 3.2.4-1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory security-tracker.debian.org