CVE-2026-57527
Zed Attack Proxy (ZAP) ViewState add-on before version 4 contains …
Zed Attack Proxy (ZAP) ViewState add-on before version 4 contains an insecure deserialization vulnerability that allows attackers who control a proxied web server to achieve arbitrary code execution by embedding a malicious serialized Java object in the javax.faces.ViewState HTTP response parameter. The JSFViewState.decode() method base64-decodes the ViewState value and passes it directly to ObjectInputStream.readObject() without a deserialization filter, allowlist, or type restriction, causing the malicious object to be deserialized within the ZAP JVM when the Desktop UI renders the ViewState panel.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/zaproxy/zap-extensions/commit/ac6c3f94d38505bc0facea286a4d3728044c6e5c
- github.com/zaproxy/zap-extensions/pull/7481
- github.com/zaproxy/zap-extensions/releases/tag/viewstate-v4
- www.vulncheck.com/advisories/zap-viewstate-add-on-insecure-deserialization-via-jsfviewstat
- www.zaproxy.org/blog/2026-06-24-java-deserialization-vulnerability-in-zap-viewstate-addon/
- nvd.nist.gov/vuln/detail/CVE-2026-57527
- cve.org/CVERecord?id=CVE-2026-57527
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.