How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "desktop"

Found 16 matching products. Filters apply to all results.

You can search for specific versions with /product/desktop/1.2.3

avira / desktop

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2005-2957	High		September 16, 2005 9/16/05	== 1.00.00.68

pgp / desktop

4 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2010-3397	High	September 15, 2010 9/15/10	== 9.9.0 == 10.0.0 == 9.10.0
CVE-2009-0681	High	April 15, 2009 4/15/09	== 8.0 == 9.0 == 9.0.6 <= 9.9.0
CVE-2008-5731	Low	December 26, 2008 12/26/08	== 9.0.6 == 9.9.0
CVE-2005-4151	Low	December 10, 2005 12/10/05	== 9.0 <= 9.0.3_build_2932 == 8.0

google / desktop

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2007-3150	High		June 11, 2007 6/11/07	*
CVE-2007-1085	High		February 23, 2007 2/23/07	*

redhat / desktop

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2008-1767	High		May 23, 2008 5/23/08	== 3

tibco / desktop

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2014-2544	High		April 10, 2014 4/10/14	<= 6.0.0

spiceworks / desktop

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2015-6021	Low		April 10, 2017 4/10/17	<= 7.5.00093

leanote / desktop

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2024-0849	Medium		February 7, 2024 2/7/24	== 2.7.0
CVE-2017-1000492	Low		January 3, 2018 1/3/18	== 2.5

docker / desktop

13 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-2664	High	February 24, 2026 2/24/26	< 4.62.0
CVE-2025-3224	High	April 28, 2025 4/28/25	< 4.41.0
CVE-2024-8695	Critical	September 12, 2024 9/12/24	< 4.34.2
CVE-2024-8696	Critical	September 12, 2024 9/12/24	< 4.34.2
CVE-2024-6222	High	July 9, 2024 7/9/24	< 4.29.0
CVE-2024-5652	Medium	July 9, 2024 7/9/24	< 4.31.0
CVE-2022-38730	Medium	April 27, 2023 4/27/23	< 4.6.0
CVE-2022-37326	High	April 27, 2023 4/27/23	< 4.6.0
CVE-2022-34292	High	April 27, 2023 4/27/23	< 4.6.0
CVE-2022-31647	High	April 27, 2023 4/27/23	< 4.6.0
CVE-2023-1802	Medium	April 6, 2023 4/6/23	== 4.17.0 == 4.17.1
CVE-2021-37841	High	August 12, 2021 8/12/21	< 3.6.0
CVE-2020-10665	Medium	March 18, 2020 3/18/20	< 2.1.0.9 < 2.2.2.0 < 2.2.0.4

oculus / desktop

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2021-24038	High		August 19, 2021 8/19/21	>= 1.39 < 31.1.0.67.507
CVE-2020-1885	High		April 8, 2020 4/8/20	< 1.44.0.32849

cybozu / desktop

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2020-5537	Critical		May 25, 2020 5/25/20	>= 2.0.23 <= 2.2.40

nextcloud / desktop

27 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-66549	Low	December 5, 2025 12/5/25	>= 3.0.0 < 3.16.5
CVE-2025-47792	Medium	May 16, 2025 5/16/25	< 3.15.0
CVE-2024-52510	Low	November 15, 2024 11/15/24	>= 3.0.0 < 3.14.2
CVE-2024-46958	Critical	September 16, 2024 9/16/24	>= 3.13.1 < 3.13.4
CVE-2024-37885	Low	June 14, 2024 6/14/24	< 3.12.0
CVE-2023-28999	Medium	April 4, 2023 4/4/23	>= 3.0.0 < 3.8.0
CVE-2023-29000	Medium	April 4, 2023 4/4/23	>= 3.0.0 < 3.7.0
CVE-2023-28997	Medium	April 4, 2023 4/4/23	>= 3.0.0 < 3.6.5
CVE-2023-28998	Medium	April 4, 2023 4/4/23	>= 3.0.0 < 3.6.5
CVE-2023-23942	Medium	February 6, 2023 2/6/23	< 3.6.3
CVE-2023-22472	Medium	January 9, 2023 1/9/23	== 3.6.1
CVE-2022-39332	Low	November 25, 2022 11/25/22	< 3.6.1
CVE-2022-39333	Low	November 25, 2022 11/25/22	< 3.6.1
CVE-2022-39331	Low	November 25, 2022 11/25/22	< 3.6.1
CVE-2022-39334	Low	November 25, 2022 11/25/22	< 3.6.1
CVE-2022-41882	Medium	November 11, 2022 11/11/22	== 3.6.0
CVE-2021-37617	High	August 18, 2021 8/18/21	>= 3.0.3 < 3.3.0
CVE-2021-32728	Medium	August 18, 2021 8/18/21	< 3.3.0
CVE-2021-22895	Medium	June 11, 2021 6/11/21	< 3.1.3
CVE-2021-22879	High	April 14, 2021 4/14/21	< 3.1.3
CVE-2020-8225	High	September 18, 2020 9/18/20	< 2.6.5
CVE-2020-8189	Medium	August 21, 2020 8/21/20	< 2.6.5
CVE-2020-8227	Medium	August 21, 2020 8/21/20	< 2.6.5
CVE-2020-8230	Medium	August 17, 2020 8/17/20	< 2.6.5
CVE-2020-8224	High	August 10, 2020 8/10/20	< 2.6.5
CVE-2020-8229	Medium	August 10, 2020 8/10/20	< 2.6.5
CVE-2020-8140	Medium	March 20, 2020 3/20/20	< 2.6.3

element / desktop

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2022-23597	High		February 1, 2022 2/1/22	< 1.9.7

asana / desktop

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2023-49314	High		November 28, 2023 11/28/23	== 2.1.0
CVE-2022-26877	Medium		April 9, 2022 4/9/22	< 1.6.0

ui / desktop

4 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2023-28124	Medium	April 19, 2023 4/19/23	< 0.62.3.0
CVE-2023-28123	Medium	April 19, 2023 4/19/23	< 0.62.3.0
CVE-2023-28122	High	April 19, 2023 4/19/23	< 0.62.3.0
CVE-2022-35257	High	September 23, 2022 9/23/22	< 0.55.3.17

pingidentity / desktop

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2022-40725	High		April 25, 2023 4/25/23	< 1.7.4

figma / desktop

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2025-56803	High		September 3, 2025 9/3/25	== 125.6.5

Showing vulnerabilities for 16 products matching "desktop". Each product has independent pagination.

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.