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.
CVE-2026-57527
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EPSS
- 36.9%
- KEV
- Not listed
Published
June 26, 2026
Last Modified
June 26, 2026
Advisory Details (5)
Auto-updated Jun 26, 2026ZAP – Java Deserialization Vulnerability in ZAP Viewstate Add-on
https://www.zaproxy.org/blog/2026-06-24-java-deserialization-vulnerability-in-zap-viewstate-addon/ZAP ViewState Add-on Insecure Deserialization via JSFViewState.decode() | Advisories | VulnCheck
https://www.vulncheck.com/advisories/zap-viewstate-add-on-insecure-deserialization-via-jsfviewstate-decodeViewState version 4
Patch available: zaproxy/zap-extensions viewstate-v4
https://github.com/zaproxy/zap-extensions/releases/tag/viewstate-v4viewstate: disable format
Patch available: zaproxy/zap-extensions viewstate-v4 (PR #7481 merged 2026-06-24)
https://github.com/zaproxy/zap-extensions/pull/7481commit ac6c3f94d385 (zaproxy/zap-extensions)
Patch available: zaproxy/zap-extensions viewstate-v4 (contains commit ac6c3f94d385)
https://github.com/zaproxy/zap-extensions/commit/ac6c3f94d38505bc0facea286a4d3728044c6e5cVendor Advisories for CVE-2026-57527(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 38× in last 7d / 58× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-06 23:32 UTCEG score recompute
- 2026-07-06 23:32 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 11:44 UTCEG score recompute
- 2026-07-06 11:44 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 23:54 UTCEG score recompute
- 2026-07-05 23:54 UTCGHSA enrichment
- 2026-07-05 12:05 UTCEG score recompute
- 2026-07-05 12:05 UTCGHSA enrichment
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-05 00:17 UTCEG score recompute
- 2026-07-05 00:17 UTCGHSA enrichment
- 2026-07-04 12:29 UTCEG score recompute
- 2026-07-04 12:29 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 00:41 UTCEG score recompute
- 2026-07-04 00:41 UTCGHSA enrichment
- 2026-07-03 12:51 UTCEG score recompute
- 2026-07-03 12:51 UTCGHSA enrichment
- 2026-07-03 01:04 UTCEG score recompute
Show 33 moreShow fewer
- 2026-07-03 01:03 UTCGHSA enrichment
- 2026-07-02 13:16 UTCEG score recompute
- 2026-07-02 13:15 UTCGHSA enrichment
- 2026-07-02 01:27 UTCEG score recompute
- 2026-07-02 01:27 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 13:40 UTCEG score recompute
- 2026-07-01 13:40 UTCGHSA enrichment
- 2026-07-01 01:52 UTCEG score recompute
- 2026-07-01 01:52 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 14:04 UTCEG score recompute
- 2026-06-30 14:04 UTCGHSA enrichment
- 2026-06-30 02:15 UTCEG score recompute
- 2026-06-30 02:15 UTCGHSA enrichment
- 2026-06-29 14:27 UTCEG score recompute
- 2026-06-29 14:27 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 02:40 UTCEG score recompute
- 2026-06-29 02:40 UTCGHSA enrichment
- 2026-06-28 14:52 UTCEG score recompute
- 2026-06-28 14:52 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 03:04 UTCEG score recompute
- 2026-06-28 03:04 UTCGHSA enrichment
- 2026-06-27 15:17 UTCEG score recompute
- 2026-06-27 15:17 UTCGHSA enrichment
- 2026-06-27 03:29 UTCEG score recompute
- 2026-06-27 03:29 UTCGHSA enrichment
- 2026-06-26 17:41 UTCNVD updateCVSS v4 → 8.7
- 2026-06-26 15:38 UTCEG score recompute
- 2026-06-26 15:38 UTCGHSA enrichment
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-20208EG 9.8CRITICAL
- CVE-2017-20207EG 9.8CRITICAL
- CVE-2017-20206EG 9.8CRITICAL
- CVE-2017-20189EG 9.8CRITICAL
- CVE-2017-10992EG 9.8EPSS 95%CRITICAL
- CVE-2013-4521EG 9.8EPSS 90%CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS 98%CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-18605EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-57527?
When was CVE-2026-57527 disclosed?
Is CVE-2026-57527 actively exploited?
What is the CVSS score of CVE-2026-57527?
How do I remediate CVE-2026-57527?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-57527
Is Your Infrastructure Affected by CVE-2026-57527?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.