Privilege Escalation Vulnerability in Screen Package

screen Updated 02 Oct 2025

Summary

26/05/2025
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2025-46802: For a short time they PTY is set to mode 666, allowing any user on the system to connect to the screen session. Affects screen versions < 4.9.1-3. Fixed in 4.9.1-3. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Screen package is a terminal multiplexer that allows users to manage multiple terminal sessions from a single interface. It is widely used in Unix-like operating systems for its ability to detach and reattach sessions, making it invaluable for remote work and long-running processes. However, a recent vulnerability has been identified that could allow unauthorized users to access screen sessions.

Vulnerability Detail

The vulnerability arises from a temporary misconfiguration where the pseudo-terminal (PTY) is set to mode 666. This mode permits any user on the system to connect to the screen session, potentially leading to unauthorized access to sensitive information or control over the session. This issue is particularly concerning in multi-user environments where privacy and security are paramount.

How To Fix

Minimum fixed version

4.9.1-3

This is the first release that contains the fix.

sudo apt-get install --only-upgrade screen

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, users can restrict access to the screen sessions by changing the permissions of the PTY or by using alternative session management tools until the package is updated.

Conclusion

The identified vulnerability in the Screen package poses a significant risk by allowing unauthorized access to screen sessions. Users are strongly advised to update to the patched version 4.9.1-3 to mitigate this risk. For ongoing monitoring of vulnerabilities, tools like Vulert can provide real-time alerts and insights.

See every vulnerability recorded for screen →

Share this vulnerability

FAQ

The vulnerability allows any user on the system to connect to a screen session due to the PTY being set to mode 666 temporarily.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected.

The risks include unauthorized access to sensitive information and control over the screen sessions, which could lead to data breaches or system compromise.

Yes, the patched version of the Screen package is 4.9.1-3. Updating to this version will resolve the vulnerability.

If immediate updates are not possible, consider using alternative session management tools or restrict access to screen sessions as a temporary measure.

Related vulnerabilities

Recent vulnerabilities recorded for screen.

How To Fix

Minimum fixed version

4.9.1-3

This is the first release that contains the fix.

sudo apt-get install --only-upgrade screen

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback