Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-0995

3.6 · LOW

An issue has been identified in Arm C1-Pro before r1p2-50eac0, where, under certain conditions, a TLBI+DSB might fail to ensure the completion of memory accesses related to SME.

Published Mar 2, 2026CWE-362EPSS 0.09%

Overview

CVE-2026-0995 is a low-severity vulnerability. It was published on March 2, 2026 and has a CVSS 3.1 base score of 3.6 (LOW).

This vulnerability has a CVSS 3.1 base score of 3.6, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical description

An issue has been identified in Arm C1-Pro before r1p2-50eac0, where, under certain conditions, a TLBI+DSB might fail to ensure the completion of memory accesses related to SME.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refdeveloper.arm.com/documentation/111823

How CyberStrike helps

Frequently asked questions

What is CVE-2026-0995?

CVE-2026-0995 is a low-severity vulnerability. It was published on March 2, 2026 and has a CVSS 3.1 base score of 3.6 (LOW).

How severe is CVE-2026-0995?

This vulnerability has a CVSS 3.1 base score of 3.6, rated LOW. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-0995?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-0995?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-0995 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999