Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-12613 Overview
CVE-2026-12613 is a deserialization of untrusted data vulnerability [CWE-502] affecting the UYAP Document Editor developed by the Turkish Ministry of Justice, General Directorate of Information Technology. The flaw permits object injection when the application processes crafted serialized data. Attackers can leverage this weakness to execute arbitrary objects within the application context, leading to compromise of confidentiality, integrity, and availability. The vulnerability affects UYAP Document Editor versions prior to 5.4.20 on Windows and Linux, and versions prior to 5.4.21 on macOS. Exploitation requires network delivery of a malicious payload and user interaction to open or process the content.
Critical Impact
Successful exploitation enables object injection that can lead to arbitrary code execution within the context of the UYAP Document Editor user, impacting judicial workstations across Windows, Linux, and macOS.
Affected Products
- UYAP Document Editor on Windows (versions before 5.4.20)
- UYAP Document Editor on Linux (versions before 5.4.20)
- UYAP Document Editor on macOS (versions before 5.4.21)
Discovery Timeline
- 2026-10-12 - CVE-2026-12613 published to NVD
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-12613
Vulnerability Analysis
The UYAP Document Editor deserializes attacker-controlled data without sufficient validation of the object graph being reconstructed. When the application rehydrates serialized objects, it instantiates classes and invokes methods whose behavior is dictated by the input stream. An attacker can craft a serialized payload referencing classes that execute undesired operations during deserialization, construction, or finalization. The result is object injection that can escalate into arbitrary code execution within the user's session. Because the editor is used to open documents and content retrieved from external sources, delivery of the malicious payload is realistic across judicial workflows.
Root Cause
The root cause is unsafe deserialization of untrusted input [CWE-502]. The application does not restrict the set of acceptable types during deserialization and does not validate the integrity or origin of the serialized stream. Any gadget chain available in the loaded runtime becomes callable through the deserialization path.
Attack Vector
The attack vector is network-based with required user interaction. An attacker delivers a crafted document or serialized blob to a target. When the user opens the content in UYAP Document Editor, the deserialization routine instantiates attacker-chosen objects, triggering the injection. No prior authentication to the target host is required.
No verified public proof-of-concept code is available at this time. Refer to the Siber Güvenlik Advisory TR-26-1299 for additional technical context.
Detection Methods for CVE-2026-12613
Indicators of Compromise
- Unexpected child processes spawned by the UYAP Document Editor process on Windows, Linux, or macOS endpoints.
- Inbound documents or attachments containing serialized object streams delivered to users of the editor.
- Outbound network connections initiated by the editor to non-UYAP infrastructure shortly after a document is opened.
Detection Strategies
- Monitor process lineage for UYAP Document Editor spawning shells, scripting interpreters, or LOLBins such as powershell.exe, cmd.exe, bash, or osascript.
- Inspect file telemetry for documents containing embedded serialized objects arriving via email, chat, or file shares targeting judicial users.
- Correlate editor execution with unusual file writes to startup, scheduled task, or autorun locations on the host.
Monitoring Recommendations
- Enforce endpoint telemetry collection on all workstations running UYAP Document Editor across Windows, Linux, and macOS.
- Alert on version strings below 5.4.20 on Windows and Linux, and below 5.4.21 on macOS, during software inventory scans.
- Track network egress from the editor process and baseline normal destinations to surface anomalies.
How to Mitigate CVE-2026-12613
Immediate Actions Required
- Upgrade UYAP Document Editor to version 5.4.20 or later on Windows and Linux hosts.
- Upgrade UYAP Document Editor to version 5.4.21 or later on macOS hosts.
- Instruct users not to open UYAP documents received from untrusted or unverified sources until patching completes.
- Validate software inventories to confirm no vulnerable builds remain in production.
Patch Information
The vendor has released fixed builds: UYAP Document Editor 5.4.20 for Windows and Linux, and UYAP Document Editor 5.4.21 for macOS. Refer to the Siber Güvenlik Advisory TR-26-1299 for authoritative version and distribution details.
Workarounds
- Restrict delivery of UYAP document files from external email senders at the mail gateway until patches are deployed.
- Apply application allowlisting to constrain child processes that the editor is permitted to spawn.
- Isolate judicial endpoints handling high-sensitivity cases on segmented network zones to limit exposure to crafted payloads.
# Configuration example: verify installed UYAP Document Editor version
# Windows (PowerShell)
Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*" |
Where-Object { $_.DisplayName -like "*UYAP*" } |
Select-Object DisplayName, DisplayVersion
# Linux
dpkg -l | grep -i uyap || rpm -qa | grep -i uyap
# macOS
mdls -name kMDItemVersion "/Applications/UYAP Document Editor.app"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

