Skip to main content
VulnerabilityPublished

CVE-2026-47313: Samsung Open Source Escargot · Excessive Memory Allocation

Affects Samsung Open Source EscargotSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.5 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Samsung Open SourceEscargotAffected
  • =590345cc6258317c5da850d846ce6baaf2afc2d3
Fixed in–

AI-suggested

Until an official fix is available, restrict local access to trusted users and limit opportunities for user interaction that could trigger the vulnerability. Monitor vendor channels for updates regarding patches or mitigations.

Description

CVE-2026-47313 is a medium severity vulnerability in Samsung Open Source Escargot involving memory allocation with an excessive size value. This flaw can lead to excessive memory allocation, potentially causing denial of service due to resource exhaustion. The vulnerability affects the specific Escargot version identified by commit 590345cc6258317c5da850d846ce6baaf2afc2d3. There is no official patch or remediation level provided by the vendor at this time, and no known exploits are reported in the wild. The vulnerability requires local access with low privileges and user interaction to trigger, and it does not impact confidentiality or integrity but affects availability.

References

Community reviews

Loading reviews…