# CVE-2025-46805: Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes wh

> A TOCTOU race in Screen allows sending signals to privileged processes when setuid-root, potentially enabling privilege escalation.

- **Severity:** Medium 5.7 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 May 2025
- **Updated:** 27 May 2025
- **Also known as:** ALPINE-CVE-2025-46805, BELL-CVE-2025-46805, DEBIAN-CVE-2025-46805, GHSA-v9hv-wgmv-7qj2, UBUNTU-CVE-2025-46805

## What is CVE-2025-46805?

CVE-2025-46805 is a medium-severity vulnerability, published on 26 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Screen version 5.0.0 and older version 4 releases have  a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes when installed setuid-root.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

## Which versions are affected by CVE-2025-46805?


## How do I fix CVE-2025-46805?

Apply the vendor's patch.

## Is CVE-2025-46805 being exploited?

There is no known exploitation of CVE-2025-46805 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-46805 and fix it if it is affected.

What it is: CVE-2025-46805 is a medium-severity vulnerability, published on 26 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46805 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-46805/ (Markdown: https://insights.sbomify.com/CVE-2025-46805/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-46805
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-46805
- OSV: https://osv.dev/vulnerability/CVE-2025-46805

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-46805/
Summaries are generated and may contain mistakes; the official description above is the record.