dbcve.org
EscargotApplication · Samsung

CVE-2026-47314

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-19
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Out-of-bounds write vulnerability in Samsung Open Source Escargot allows Overflow Buffers. This issue affects Escargot: 590345cc6258317c5da850d846ce6baaf2afc2d3.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An out-of-bounds write vulnerability exists in Samsung's Escargot JavaScript engine at a specific commit (590345cc6258317c5da850d846ce6baaf2afc2d3). The vulnerability allows a buffer overflow condition where memory can be written beyond allocated buffer boundaries, potentially enabling arbitrary code execution or denial of service.

MitigationUpdate Escargot to the latest version once a patch is released. If immediate patching is not possible, restrict network exposure of systems running Escargot and monitor for signs of exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EscargotApplication
Affected:= 2026-05-14

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Escargot JavaScript engine presence
    Locate Escargot binaries, libraries, or applications using it. Common locations: /usr/lib/libescargot*, checking Samsung application directories, or searching for files named 'escargot' or 'Escargot'. Also check running processes for escargot-related entries.
    Affected if Escargot is found in the environment
  2. Determine Escargot version
    Run 'escargot --version' or check the binary/library version metadata. If built from source, check git log for commit hash using 'git log -1 --format=%H' in the source directory.
    Affected if Version cannot be determined or version display fails
  3. Compare against affected version 2026-05-14
    Compare your detected version string to '2026-05-14'. Exact match means affected. Note: This is a specific date-based version, not a range.
    Affected if Installed version equals exactly 2026-05-14
  4. Check git commit hash if applicable
    If you have access to the source code or built binaries, verify the commit hash. The vulnerable commit is 590345cc6258317c5da850d846ce6baaf2afc2d3. Use 'git rev-parse HEAD' in the source directory or inspect binary embedded version info.
    Affected if Commit hash matches 590345cc6258317c5da850d846ce6baaf2afc2d3

If your Escargot installation is version 2026-05-14 or at commit 590345cc6258317c5da850d846ce6baaf2afc2d3, the out-of-bounds write vulnerability is present in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Update Escargot to the latest version once a patch is released. If immediate patching is not possible, restrict network exposure of systems running Escargot and monitor for signs of exploitation.

Recommended fix High confidence

Any Escargot release/commit after 590345cc6258317c5da850d846ce6baaf2afc2d3 that includes the PR #1565 fix

  1. 1. Identify the current Escargot version in use (2026-05-14)
  2. 2. Navigate to the Escargot GitHub repository at https://github.com/Samsung/escargot
  3. 3. Review the patch details in pull request #1565 to understand the security fix
  4. 4. Upgrade to a version of Escargot that includes the fix from PR #1565 (a version/commit after 590345cc6258317c5da850d846ce6baaf2afc2d3)
  5. 5. Verify the upgrade by checking the Escargot version and confirming the vulnerability is resolved
Caveat Review release notes for any breaking changes between 2026-05-14 and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Escargot Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47314 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47314 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data