CVE-2021-26937: encoding.c in GNU Screen through 4.8.0 allows remote attackers to cause a denial of service (invalid write access and application crash) or
Noroxi assessment
Priority: Plan (action score 42/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 9.1% (FIRST EPSS); higher than 95.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: screen (Alpine:v3.10) 4.6.2-r2; screen (Alpine:v3.11) 4.7.0-r2; screen (Alpine:v3.12) 4.8.0-r1.
Add it to your regular patch cycle. Upgrade to screen (Alpine:v3.10) 4.6.2-r2; screen (Alpine:v3.11) 4.7.0-r2; screen (Alpine:v3.12) 4.8.0-r1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
encoding.c in GNU Screen through 4.8.0 allows remote attackers to cause a denial of service (invalid write access and application crash) or possibly have unspecified other impact via a crafted UTF-8 character sequence.
- Published
- Feb 9, 2021
- Updated
- Jun 16, 2026
- EPSS
- 9.1% · 95th percentile
- CWE
- CWE-88
Report tools
Action score
42
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 9.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| gnu | screen | cpe:2.3:a:gnu:screen |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux10.0
- debian debian linux9.0
- fedoraproject fedora32
- fedoraproject fedora33
- gnu screenup to 4.8.0 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | screen | before 4.6.2-r2 | 4.6.2-r2 |
| Alpine:v3.11 | screen | before 4.7.0-r2 | 4.7.0-r2 |
| Alpine:v3.12 | screen | before 4.8.0-r1 | 4.8.0-r1 |
| Alpine:v3.13 | screen | before 4.8.0-r4 | 4.8.0-r4 |
| Debian:10 | screen | before 4.6.2-3+deb10u1 | 4.6.2-3+deb10u1 |
| Debian:12 | screen | before 4.8.0-5 | 4.8.0-5 |
| Debian:9 | screen | before 4.5.0-6+deb9u1 | 4.5.0-6+deb9u1 |
| openSUSE:Leap 15.2 | screen | before 4.6.2-lp152.6.3.1 | 4.6.2-lp152.6.3.1 |
| openSUSE:Tumbleweed | screen | before 4.9.0-1.1 | 4.9.0-1.1 |
| Red Hat:enterprise_linux:7::client | screen | before 0:4.1.0-0.27.20120314git3c2946.el7_9 | 0:4.1.0-0.27.20120314git3c2946.el7_9 |
| Red Hat:enterprise_linux:7::client | screen-debuginfo | before 0:4.1.0-0.27.20120314git3c2946.el7_9 | 0:4.1.0-0.27.20120314git3c2946.el7_9 |
| Red Hat:rhel_aus:7.7::server | screen | before 0:4.1.0-0.25.20120314git3c2946.el7_7.1 | 0:4.1.0-0.25.20120314git3c2946.el7_7.1 |
| Red Hat:rhel_aus:7.7::server | screen-debuginfo | before 0:4.1.0-0.25.20120314git3c2946.el7_7.1 | 0:4.1.0-0.25.20120314git3c2946.el7_7.1 |
| SUSE:HPE Helion OpenStack 8 | screen | before 4.0.4-23.6.1 | 4.0.4-23.6.1 |
| SUSE:Linux Enterprise Module for Basesystem 15 SP2 | screen | before 4.6.2-5.3.1 | 4.6.2-5.3.1 |
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2003-0972Integer signedness error in ansi.c for GNU screen 4.0.1 and earlier, and 3.9.15 and earlier, allows local users to execute arbitrary code vi41Plan
- CVE-2020-9366A buffer overflow was found in the way GNU Screen before 4.8.0 treated the special escape OSC 49.40Plan
- CVE-2017-5618GNU screen before 4.5.1 allows local users to modify arbitrary files and consequently gain root privileges by leveraging improper checking o31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2007-3048Jun 5, 2007 · GNU screen 4.0.3 allows local users to unlock the screen via a CTRL-C sequence at the password prompt.28Monitor
- ← EarlierCVE-2009-1214Apr 1, 2009 · GNU screen 4.0.3 creates the /tmp/screen-exchange temporary file with world-readable permissions, which might allow local users to obtain se19Monitor
- Later →CVE-2023-24626Apr 8, 2023 · socket.c in GNU Screen through 4.9.0, when installed setuid or setgid (the default on platforms such as Arch Linux and FreeBSD), allows loca26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:screen | 4.6.2-r2 · Alpine:v3.10 | Package registry (OSV) |
| debian:screen | 4.8.0-5 · Debian:12 | Package registry (OSV) |
| opensuse:screen | 4.6.2-lp152.6.3.1 · openSUSE:Leap 15.2 | Package registry (OSV) |
| red hat:screen | 0:4.1.0-0.27.20120314git3c2946.el7_9 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:screen-debuginfo | 0:4.1.0-0.27.20120314git3c2946.el7_9 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:screen | 4.0.4-23.6.1 · SUSE:HPE Helion OpenStack 8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Parameter InjectionCAPEC-137likelihood: Medium · Medium
- Flash Parameter InjectionCAPEC-174likelihood: High · Medium
- Using Meta-characters in E-mail Headers to Inject Malicious PayloadsCAPEC-41likelihood: High · High
- HTTP Parameter Pollution (HPP)CAPEC-460Medium
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- lists.debian.org/debian-lts-announce/2021/02/msg00031.html
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/GNWBOIDEPOEQS5RMQVMFKHKXJCGNYWBL/
- lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/JJWLXP45POUUYBJRRWPVAWNZDJTLYWVM/
- security.gentoo.org/glsa/202105-11
- www.debian.org/security/2021/dsa-4861
- security.netapp.com/advisory/ntap-20250509-0004/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.