Cyber Resilience

CVE-2026-25204

Deserialization in Samsung Escargot ≤ 2026-03-28

DeserializationMemory Safety
Published
13 April 2026
Modified
02 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0030 23th percentile
Risk Priority 47 floored blend · peak EPSS

Summary

CVE-2026-25204 is a medium-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Samsung Escargot. Its CVSS base score is 6.2 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 23th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A08:2025 Software or Data Integrity Failures

EU & UK References

Vulnerability Data

Deserialization of untrusted data vulnerability in Samsung Open Source Escargot Java Script allows denial of service condition via process abort. This issue affects escarogt prior to commit hash 97e8115ab1110bc502b4b5e4a0c689a71520d335

CWE(s)
CWE-502CWE-843

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-40446Same product: Samsung Escargot
CVE-2026-47311Same product: Samsung Escargot
CVE-2026-47310Same product: Samsung Escargot
CVE-2026-40447Same product: Samsung Escargot
CVE-2026-8915Same product: Samsung Escargot
CVE-2026-47316Same product: Samsung Escargot
CVE-2026-47314Same product: Samsung Escargot
CVE-2024-32671Same product: Samsung Escargot
CVE-2023-41268Same product: Samsung Escargot
CVE-2026-47312Same product: Samsung Escargot

Affected Assets

samsung
escargot
≤ 2026-03-28

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V3.2.3
  • V15.3.5

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can uncover deserialization flaws before deployment.

SI-10 Information Input Validation good match

Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

SI-16 Memory Protection partial match

Memory-protection controls limit the blast radius when a type-confusion access occurs but do not stop the flaw itself.

SI-7 Software, Firmware, and Information Integrity partial match

Integrity verification tools can detect malformed or tampered serialized data after the fact.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.

PR.PS-02 none match
prevents

PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong typing and interface contracts that reduce type confusion.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.

A.8.28 Secure coding partial match
prevents

Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.

A.8.8 Management of technical vulnerabilities partial match
finds

Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.

References