# CVE-2026-59081: Deserialization of untrusted data in Edito CMS

Status: published. Published: 2026-11-13. Updated: 2026-11-13.

Edito CMS deserializes JSON data without further validation. A user (even an administrator) cannot exploit this vulnerability through the application's normal functionality. An attacker who could modify cache entries or inject them could execute code on the server.




This issue was fixed in version 5.10.2607.  Hotfixes for older versions (5.8) have also been released.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Edito / Edito CMS: ≥ 0; < 5.10.2607 (affected, semver). Source: CNA: CERT-PL

## Severity and prioritization

- CVSS 4.0: 8.4 (high); CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L; source: CNA: CERT-PL

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-502

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://cert.pl/posts/2026/07/CVE-2026-59081 (CNA: CERT-PL)

- https://www.edito.pl/ (CNA: CERT-PL)

## Provenance

- CNA: CERT-PL: https://www.cve.org/CVERecord?id=CVE-2026-59081; retrieved 2026-11-13; source updated 2026-11-13

Revision: 00745da9f505dc5611fc118ea49b5b9dcee4eac27eb9b34d5e45d09114406ea2

Canonical: https://y2.dev/cve/CVE-2026-59081

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.