How severe is CVE-2022-2995?

CVE-2022-2995 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2022-2995 being actively exploited?

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

What products are affected by CVE-2022-2995?

CVE-2022-2995 affects Kubernetes Cri-o. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-2995?

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

When was CVE-2022-2995 published?

CVE-2022-2995 was published on 2022-09-19 and last updated on 2026-06-17.

CVE-2022-2995

CVE-2022-2995 is a high-severity vulnerability in Kubernetes Cri-o with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-732.

Key facts

Severity: High (CVSS 3.x base score 7.1)
EPSS exploit prediction: 0% (29th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-732
Affected product: Kubernetes Cri-o
Published: 2022-09-19
Last modified: 2026-06-17

Description

Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.

Frequently asked questions

What is CVE-2022-2995?: Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.
How severe is CVE-2022-2995?: CVE-2022-2995 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2022-2995 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (29th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-2995?: CVE-2022-2995 affects Kubernetes Cri-o. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-2995?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-2995 published?: CVE-2022-2995 was published on 2022-09-19 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:kubernetes:cri-o:1.25.0:*:*:*:*:*:*:*

More vulnerabilities in Kubernetes Cri-o

CVE-2022-0811 — High (CVSS 8.8): A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a…
CVE-2018-1000400 — High (CVSS 8.8): Kubernetes CRI-O version prior to 1.9 contains a Privilege Context Switching Error (CWE-270) vulnerability in the…
CVE-2024-5154 — High (CVSS 8.1): A flaw was found in cri-o. A malicious container can create a symbolic link to arbitrary files on the host via…
CVE-2022-4318 — High (CVSS 7.8): A vulnerability was found in cri-o. This issue allows the addition of arbitrary lines into /etc/passwd by use of a…
CVE-2022-1708 — High (CVSS 7.5): A vulnerability was found in CRI-O that causes memory or disk space exhaustion on the node for anyone with access to…
CVE-2022-27652 — Medium (CVSS 5.3): A flaw was found in cri-o, where containers were incorrectly started with non-empty default permissions. A…

All CVEs affecting Kubernetes Cri-o →

Other CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities

CVE-2026-9508 — Critical (CVSS 10.0): Incorrect permission settings on a critical resource in Suprema BioStar 2 (versions 2.9.3 through 2.9.11) that allow…
CVE-2025-14988 — Critical (CVSS 10.0): A security issue has been identified in ibaPDA that could allow unauthorized actions on the file system under certain…
CVE-2025-69426 — Critical (CVSS 10.0): The Ruckus vRIoT IoT Controller firmware versions prior to 3.0.0.0 (GA) contain hardcoded credentials for an operating…
CVE-2025-12004 — Critical (CVSS 10.0): Incorrect Permission Assignment for Critical Resource vulnerability in The Wikimedia Foundation Mediawiki - Lockdown…
CVE-2014-125121 — Critical (CVSS 10.0): Array Networks vAPV (version 8.3.2.17) and vxAG (version 9.2.0.34) appliances are affected by a privilege escalation…
CVE-2025-46093 — Critical (CVSS 9.9): LiquidFiles before 4.1.2 supports FTP SITE CHMOD for mode 6777 (setuid and setgid), which allows FTPDrop users to…

Browse all CWE-732 (Incorrect Permission Assignment for Critical Resource) vulnerabilities →