How many CVEs have patched run?

9 published CVEs changed run in Samsung/escargot, in 1 distinct patches totalling 54 changed lines, between 2026 and 2026.

What is the latest CVE that changed run?

CVE-2026-47317, published 2026-05-19, changed lines 114 to 131 of src/runtime/SandBox.cpp.

How does run compare to the rest of Samsung/escargot?

Samsung/escargot has 31 CVEs with a located fix in total; 9 of them changed run.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

Samsung/escargot

Function

run

Name: run in Samsung/escargot: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

src/runtime/SandBox.cpp

Last patched May 19, 2026

9

CVEs

That changed this function

1

Distinct patches

Backports counted once

54

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

run in Samsung/escargot was changed by 9 published CVE fixes in 2026, in 1 distinct patches that added or removed 54 lines in total.

Samsung/escargot has 31 CVEs with a located fix in total, so 29% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed run, newest first, with the lines each fix touched.

CVE-2026-47317
CVE-2026-47317 · lines 114–131 · +6 −0 in 2 hunks
High · CVSS 7.5
EPSS 0.3%2026-05-19
CVE-2026-47316
CVE-2026-47316 · lines 114–131 · +6 −0 in 2 hunks
High · CVSS 7.5
EPSS 0.3%2026-05-19
CVE-2026-47315
CVE-2026-47315 · lines 114–131 · +6 −0 in 2 hunks

High · CVSS 7.5

EPSS 0.3%2026-05-19

CVE-2026-47314

CVE-2026-47314 · lines 114–131 · +6 −0 in 2 hunks

Critical · CVSS 9.8

EPSS 0.3%2026-05-19

CVE-2026-47313

CVE-2026-47313 · lines 114–131 · +6 −0 in 2 hunks

High · CVSS 7.5

EPSS 0.3%2026-05-19

CVE-2026-47312

CVE-2026-47312 · lines 114–131 · +6 −0 in 2 hunks

High · CVSS 7.5

EPSS 0.3%2026-05-19

CVE-2026-47311

CVE-2026-47311 · lines 114–131 · +6 −0 in 2 hunks

Critical · CVSS 9.8

EPSS 0.3%2026-05-19

CVE-2026-47310

CVE-2026-47310 · lines 114–131 · +6 −0 in 2 hunks

Critical · CVSS 9.8

EPSS 0.3%2026-05-19

CVE-2026-47309

CVE-2026-47309 · lines 114–131 · +6 −0 in 2 hunks

High · CVSS 7.5

EPSS 0.3%2026-05-19

Get an alert when the next CVE fix lands in Samsung/escargot, with the patched functions.

Monitor escargot CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in Samsung/escargot changed by the most CVE fixes.

parse10 CVEs · src/runtime/JSON.cpp loadStringTable9 CVEs · src/codecache/CodeCacheReaderWriter.cpp iterableToList9 CVEs · src/runtime/IteratorObject.cpp initialize9 CVEs · src/heap/Heap.cpp finalizer9 CVEs · src/runtime/FinalizationRegistryObject.cpp builtinTypedArrayCopyWithin9 CVEs · src/builtins/BuiltinTypedArray.cpp

All patched functions in Samsung/escargot

Frequently asked questions

Common questions about CVE fixes to run.

How many CVEs have patched run?: 9 published CVEs changed run in Samsung/escargot, in 1 distinct patches totalling 54 changed lines, between 2026 and 2026.
What is the latest CVE that changed run?: CVE-2026-47317, published 2026-05-19, changed lines 114 to 131 of src/runtime/SandBox.cpp.
How does run compare to the rest of Samsung/escargot?: Samsung/escargot has 31 CVEs with a located fix in total; 9 of them changed run.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track Samsung/escargot CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing