CVE-2026-47311
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 · uneditedHeap-based buffer overflow 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 confidenceHeap-based buffer overflow vulnerability in Samsung's Escargot JavaScript engine allows overflowing buffers on the heap memory region. This memory corruption issue could potentially allow an attacker to overwrite adjacent memory structures.
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= 2026-05-14CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Escargot is installedCheck for Escargot binary, library, or any application that embeds Escargot JavaScript engine. Look for process named 'escargot' or check for Escargot library files (libescargot.so, escargot.dll, or similar).Affected if Escargot is present in the environment
-
Determine Escargot versionRun 'escargot --version' if CLI is available, or inspect the Escargot library binary for version metadata. If building from source, check git log or git rev-parse HEAD to obtain the commit hash.Affected if Cannot determine version or commit hash and Escargot is in use
-
Compare against affected versionCheck if the installed version string equals '2026-05-14' or if the git commit hash matches 590345cc6258317c5da850d846ce6baaf2afc2d3.Affected if Version is exactly 2026-05-14 or commit hash is 590345cc6258317c5da850d846ce6baaf2afc2d3
Environment is affected if Samsung Escargot version is exactly 2026-05-14 or includes the vulnerable commit 590345cc6258317c5da850d846ce6baaf2afc2d3.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Escargot to a patched version beyond commit 590345cc6258317c5da850d846ce6baaf2afc2d3, or apply source-level fixes with proper bounds checking in the affected code paths.
- Review the vulnerability details for CVE-2026-47311 affecting Escargot version 2026-05-14 (commit 590345cc6258317c5da850d846ce6baaf2afc2d3)
- Navigate to the vendor patch at https://github.com/Samsung/escargot/pull/1565
- Examine the changes introduced in PR #1565 to understand the security fix
- Apply the patch from PR #1565 to the affected Escargot codebase
- Rebuild and test the Escargot engine after applying the patch
- Verify the heap-based buffer overflow vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47311 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47311 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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