Local root escalation via unbounded password input
Published Mar 13, 2026 · Updated Mar 13, 2026
Classic buffer overflow in AT&T Bell Labs UNIX 4 su allows local users to gain root privileges through an overlong password. The su.c input loop writes getchar() bytes into the fixed 100-byte password array until newline or NUL without tracking its length. The setuid-root command is locally reachable without the root password; adjacent-memory corruption grants a root shell, although the published demonstration confirms only a crash.
Summary
What happened
Classic buffer overflow in AT&T Bell Labs UNIX 4 su allows local users to gain root privileges through an overlong password. The su.c input loop writes getchar() bytes into the fixed 100-byte password array until newline or NUL without tracking its length. The setuid-root command is locally reachable without the root password; adjacent-memory corruption grants a root shell, although the published demonstration confirms only a crash.
The record
- CVE
- CVE-2025-71263
- Published
- Mar 13, 2026
- Updated
- Mar 13, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2026CVE publishedPublication date reported by the CVE source.
- Mar 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo