Menu

Star on GitHub · 3.2k

CVE-2026-5398

8.4 · HIGH

The implementation of TIOCNOTTY failed to clear a back-pointer from the structure representing the controlling terminal to the calling process' session.

Published Apr 22, 2026CWE-416EPSS 0.18%

Overview

CVE-2026-5398 is a high-severity vulnerability. It was published on April 22, 2026 and has a CVSS 3.1 base score of 8.4 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.4, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

The implementation of TIOCNOTTY failed to clear a back-pointer from the structure representing the controlling terminal to the calling process' session. If the invoking process then exits, the terminal structure may end up containing a pointer to freed memory.

A malicious process can abuse the dangling pointer to grant itself root privileges.

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.

Frequently asked questions

What is CVE-2026-5398?

CVE-2026-5398 is a high-severity vulnerability. It was published on April 22, 2026 and has a CVSS 3.1 base score of 8.4 (HIGH).

How severe is CVE-2026-5398?

This vulnerability has a CVSS 3.1 base score of 8.4, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

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

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-5398?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-5398 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 HIGH CVEs from 2026

View all