vciy

CVE-2021-20315

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

A locking protection bypass flaw was found in some versions of gnome-shell as shipped within CentOS Stream 8, when the "Application menu" or "Window…

CVE-2021-203154 of 4 sources documented this
19

rank 19 = 0 + 15 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00196  ·  without this subject the record ranks 19

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.1, from NVD  ·  without this subject the record ranks 4

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 19

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 15

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 19

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$8,620over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$8,620 = $4.99M incident cost x 0.8814887365328109 exposure x 0.00196 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00196EPSSNOT IN KEVas of 2026-09-20
Severity6.1 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementfallenreceipt
PLATEAU10Minimal movement since 2022-02-19, 1602 days at 0.00, as of 2026-07-10. arc-rules@v1

Foresight · where to check next

This record is one instance of CWE-667, improper locking. The index holds 739 prior instances of this class, 2 KEV-listed. taxonomy@v1

Full pattern panel

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running gnome-shell? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds physical access · no privileges required · no user interaction · low attack complexityreceipt
ImpactComplete integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-667 Improper Lockingreceipt
Published consequencesCWE-667: Availability: DoS: Resource Consumption (CPU)[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

First unaffected version, by branchgnome-shell 3.32.2receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, NVD6.1 MEDIUMreceipt
Exploit probability0.00196 · top 90% of all CVEsreceipt
Blast breadth2 products across 2 vendorsderived
Assigned byredhatreceipt
Recorded changes13 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productgnome-shellreceipt
Published rangesgnome-shell < 3.32.2; centos stream 8receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

A locking protection bypass flaw was found in some versions of gnome-shell as shipped within CentOS Stream 8, when the "Application menu" or "Window list" GNOME extensions are enabled. This flaw allows a physical attacker who has access to a locked system to kill existing applications and start new ones as the locked user, even if the session is still locked. receipt

NVD's analysis a second authority

severity
6.1 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
weakness
CWE-667
affected versions
gnome-shell < 3.32.2; centos stream 8

check it yourself bugzilla.redhat.com receipt

Movement the material steps

19 Feb 20220.00885
7 Mar 20234.5e-4 · scoring model v2023.03.01
17 Mar 20250.00038 · scoring model v2025.03.14
15 Jun 20260.00188 · scoring model v2026.06.15
10 Jul 20260.00196
Show all 13 observations
19 Feb 20220.00885
7 Mar 20234.5e-4
8 Mar 20230.00045
1 Aug 20230.00050
11 Sep 20230.00051
3 Nov 20240.00058
17 Mar 20250.00038
29 Mar 20250.00052
30 Mar 20250.00038
15 Jan 20260.00029
15 Jun 20260.00188
19 Jun 20260.00193
10 Jul 20260.00196

13 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00196Published2022-02-18Index as of2026-07-10

The record had been public for 4 years, 4 months when this index was last written.

Published 2022-02-18 receipt · Index as of 2026-07-10 derived

The pattern, elsewhere

This record is one instance of CWE-667, improper locking. The index holds 739 prior instances of this class, 2 KEV-listed. [email protected]

CVE-2025-43510 · Apple iOS and iPadOSmatches 5 of 9KEV listed · 2025receipt
CVE-2021-1782 · Apple iOS and iPadOSmatches 4 of 9KEV listed · 2021receipt

739 records in this class held. The six above are ranked by exploit maturity, then recency.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2021-20315.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.