How severe is CVE-2018-19333?

CVE-2018-19333 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2018-19333 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2018-19333?

CVE-2018-19333 affects Google Gvisor. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2018-19333?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2018-19333 published?

CVE-2018-19333 was published on 2018-11-17 and last updated on 2026-06-17.

CVE-2018-19333

CVE-2018-19333 is a critical-severity vulnerability in Google Gvisor with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 1% (53rd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Google Gvisor
Published: 2018-11-17
Last modified: 2026-06-17

Description

pkg/sentry/kernel/shm/shm.go in Google gVisor before 2018-11-01 allows attackers to overwrite memory locations in processes running as root (but not escape the sandbox) via vectors involving IPC_RMID shmctl calls, because reference counting is mishandled.

Frequently asked questions

What is CVE-2018-19333?: pkg/sentry/kernel/shm/shm.go in Google gVisor before 2018-11-01 allows attackers to overwrite memory locations in processes running as root (but not escape the sandbox) via vectors involving IPC_RMID shmctl calls, because reference counting is mishandled.
How severe is CVE-2018-19333?: CVE-2018-19333 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-19333 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (53rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-19333?: CVE-2018-19333 affects Google Gvisor. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-19333?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2018-19333 published?: CVE-2018-19333 was published on 2018-11-17 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:google:gvisor:*:*:*:*:*:*:*:*

More vulnerabilities in Google Gvisor

CVE-2025-2713 — High (CVSS 7.8): Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file…
CVE-2018-16359 — Medium (CVSS 6.8): Google gVisor before 2018-08-23, within the seccomp sandbox, permits access to the renameat system call, which allows…
CVE-2018-20168 — Medium (CVSS 5.5): Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact, which…
CVE-2024-10603 — Medium (CVSS 5.3): Weaknesses in the generation of TCP/UDP source ports and some other header values in Google's gVisor allowed them to be…
CVE-2024-10026 — Medium (CVSS 5.3): A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to calculate…
CVE-2023-7258 — Medium (CVSS 4.8): A denial of service exists in Gvisor Sandbox where a bug in reference counting code in mount point tracking could lead…

All CVEs affecting Google Gvisor →