CVE-2026-47310
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 · uneditedUse after free vulnerability in Samsung Open Source Escargot allows Pointer Manipulation. 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 confidenceUse-after-free vulnerability in Samsung's Escargot JavaScript engine allows pointer manipulation, enabling an attacker to potentially execute arbitrary code via the freed memory reference.
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.
-
Identify Escargot version in useCheck the application's binary or library for version metadata, or query the Escargot runtime via JavaScript (e.g., check for version properties if exposed, or inspect the compiled binary strings for the date '2026-05-14')Affected if The installed Escargot version is exactly 2026-05-14
-
Confirm Escargot is the active JavaScript engineReview application dependencies and identify which JavaScript engine is loaded at runtime; check process memory or loaded libraries for 'Escargot' stringsAffected if Escargot is the JavaScript engine powering the application
-
Determine if untrusted JavaScript execution is possibleInspect application code paths that accept and execute JavaScript input; check if user-supplied or external JavaScript code can be passed to the Escargot engineAffected if The application allows untrusted JavaScript to be executed by Escargot without sanitization or sandboxing
-
Check for pointer manipulation opportunitiesReview memory allocation patterns in code using Escargot; examine whether the application creates objects that could be freed while still referencedAffected if The application performs memory operations where freed pointers could be accessed after deallocation
You are affected if your environment uses Escargot version 2026-05-14 and allows untrusted JavaScript to be executed, enabling the use-after-free to be triggered.
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 version beyond the vulnerable commit (590345cc6258317c5da850d846ce6baaf2afc2d3) after the vendor releases a patch. If no patch is available, consider mitigating exposure by restricting untrusted JavaScript execution.
- Locate the Escargot source code at commit 590345cc6258317c5da850d846ce6baaf2afc2d3 (version 2026-05-14)
- Apply the changes from GitHub pull request #1565 (https://github.com/Samsung/escargot/pull/1565) to address the use-after-free vulnerability
- Rebuild the Escargot library with the patched code
- Verify the fix resolves the pointer manipulation issue by running existing test cases
- Ensure no regressions in JavaScript engine functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing12.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 $6,976.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47310 — 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-47310 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