Vulnerability Database

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "server"

Found 27 matching products. Filters apply to all results.

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

vmware / server

58 vulnerabilities found
Title Severity Exploit Date Affected Version
High December 6, 2010 12/6/10
== 2.0.0
== 2.0.1
== 2.0.2
Medium December 6, 2010 12/6/10
== 2.0.2
High December 6, 2010 12/6/10
== 2.0.2
Medium April 27, 2010 4/27/10
== 2.0.0
== 2.0.1
== 2.0.2
High April 12, 2010 4/12/10
== 2.0.0
== 2.0.1
== 2.0.2
High April 12, 2010 4/12/10
== 2.0.0
== 2.0.1
== 2.0.2
High April 12, 2010 4/12/10
>= 2.0.0 <= 2.0.2
Medium April 12, 2010 4/12/10
== 2.0.0
== 2.0.1
== 2.0.2
High April 12, 2010 4/12/10
== 2.0.0
== 2.0.1
== 2.0.2
High April 12, 2010 4/12/10
== 2.0.0
== 2.0.1
== 2.0.2
High April 12, 2010 4/12/10
== 2.0.0
== 2.0.1
== 2.0.2
High April 1, 2010 4/1/10
== 2.0.0
Low April 1, 2010 4/1/10
== 1.0
Low April 1, 2010 4/1/10
== 2.0.0
Low December 16, 2009 12/16/09
== 2.0.2
Medium November 2, 2009 11/2/09
== 1.0.9
== 1.0.1
== 1.0.2
== 1.0.8
== 2.0-rc2
== 1.0.4
== 1.0.7
== 2.0.1
== 2.0
== 1.0.3
== 1.0.6
== 1.0
== 1.0.5
Medium November 2, 2009 11/2/09
== 1.0.9
== 1.0.1_build_29996
== 1.0.1
== 1.0.2
== 1.0.8
== 1.0.4
== 1.0.7
== 1.0.4_build_56528
== 1.0.3
== 1.0.6
== 1.0
== 1.0.5
== 2.0.0
== 2.0.1
Medium October 16, 2009 10/16/09
== 2.0.0
== 2.0.1
== 2.0.2
Low June 1, 2009 6/1/09
<= 1.0.8
== 1.0
== 1.0.1
== 1.0.1_build_29996
== 1.0.2
== 1.0.3
== 1.0.4
== 1.0.4_build_56528
== 1.0.5
== 1.0.6
== 1.0.7
== 2.0
Medium April 13, 2009 4/13/09
== 1.0.9
== 1.0.1
== 1.0.2
== 1.0.8
== 1.0.4
== 1.0.7
== 2.0
== 1.0.3
== 1.0.6
== 1.0
== 1.0.5
High April 6, 2009 4/6/09
== 2.0
Medium April 6, 2009 4/6/09
== 2.0
Low April 6, 2009 4/6/09
== 1.0.1
== 1.0.2
== 1.0.8
== 1.0.4
== 1.0.7
== 2.0
== 1.0.3
== 1.0.6
== 1.0
== 1.0.5
High April 6, 2009 4/6/09
== 2.0
Low March 25, 2009 3/25/09
== 2.0.0
High March 12, 2009 3/12/09
== 2.0.0
Medium January 20, 2009 1/20/09
== 2.0.0
High December 9, 2008 12/9/08
>= 1.0 <= 1.0.9
Medium November 10, 2008 11/10/08
>= 1.0 <= 1.0.7
Medium October 6, 2008 10/6/08
>= 1.0 < 1.0.8
High September 3, 2008 9/3/08
< 1.0.7
High September 3, 2008 9/3/08
< 1.0.7
High September 3, 2008 9/3/08
< 1.0.7
High September 3, 2008 9/3/08
< 1.0.7
High September 3, 2008 9/3/08
< 1.0.7
High September 3, 2008 9/3/08
< 1.0.7
Medium September 3, 2008 9/3/08
== 1.0.1_build_29996
== 1.0.4_build_56528
== 1.0.3
High September 3, 2008 9/3/08
< 1.0.7
High September 3, 2008 9/3/08
< 1.0.7
Low June 5, 2008 6/5/08
== 1.0.3
Medium June 5, 2008 6/5/08
== 1.0.3
High June 5, 2008 6/5/08
<= 1.0.5
High March 20, 2008 3/20/08
== 1.0.3
Medium March 20, 2008 3/20/08
== 1.0.3
High March 20, 2008 3/20/08
== 1.0.3
High March 20, 2008 3/20/08
>= 1.0 < 1.0.5
High March 20, 2008 3/20/08
== 1.0.3
High October 21, 2007 10/21/07
< 1.0.4
High October 21, 2007 10/21/07
<= 1.0.3
High September 21, 2007 9/21/07
>= 1.0 < 1.0.4

prorat / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
High March 20, 2007 3/20/07
== 1.9-fix2

anti-spam_smtp_proxy / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
High August 10, 2007 8/10/07
== 1.3.3

microsoft / server

3 vulnerabilities found
Title Severity Exploit Date Affected Version
High September 11, 2008 9/11/08
== 2008
High September 11, 2008 9/11/08
== 2008
== 2003-sp1
== 2003-sp2
High September 11, 2008 9/11/08
== 2008

activepdf / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
High February 28, 2008 2/28/08
<= 3.8.5.14
<= 3.8.4

zend / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium September 24, 2011 9/24/11
== 5.1.0

trueconf / server

13 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium December 30, 2025 12/30/25
== 5.5.2.10813
High December 30, 2025 12/30/25
== 5.5.2.10813
High December 30, 2025 12/30/25
== 5.5.2.10813
Critical December 27, 2022 12/27/22
< 5.2.6
High December 27, 2022 12/27/22
< 5.2.6
Low June 29, 2022 6/29/22
== 4.3.7.12255
== 4.3.7.12219
Low June 29, 2022 6/29/22
< 5.0.2
Low June 29, 2022 6/29/22
< 5.0.2
Low June 29, 2022 6/29/22
< 5.0.2
Low June 29, 2022 6/29/22
< 5.0.2
Low June 29, 2022 6/29/22
< 5.0.2
Low June 29, 2022 6/29/22
< 5.0.2
Low June 29, 2022 6/29/22
< 5.0.2

icewarp / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
Low August 31, 2017 8/31/17
== 11.3.1.5

traccar / server

2 vulnerabilities found
Title Severity Exploit Date Affected Version
High January 9, 2019 1/9/19
== 4.2
High December 20, 2018 12/20/18
<= 4.0

octopus / server

9 vulnerabilities found
Title Severity Exploit Date Affected Version
Low May 4, 2022 5/4/22
>= 2022.1 < 2022.1.2454
>= 2021.3 < 2021.3.12725
High July 8, 2021 7/8/21
>= 2021.1.0 < 2021.1.7316
< 2020.6.5146
High July 8, 2021 7/8/21
>= 2020.6.0 < 2020.6.5146
>= 2021.1.0 < 2021.1.7316
Low June 17, 2021 6/17/21
>= 2020.0.0 < 2020.6.0
>= 2020.6.0 < 2020.6.5146
>= 2021.1.0 < 2021.1.7316
>= 2018.9.17 < 2018.13.0
High May 14, 2021 5/14/21
>= 2021.1.0 < 2021.1.6959
>= 2020.6.0 < 2020.6.4847
< 2020.5.329
Low August 25, 2020 8/25/20
== 3.4.0
Medium November 18, 2019 11/18/19
>= 3.4.0 <= 2019.10.5
Low August 23, 2019 8/23/19
>= 2018.8.4 <= 2019.7.6
Low August 23, 2019 8/23/19
>= 3.0.8 <= 2019.7.6

nextcloud / server

2 vulnerabilities found
Title Severity Exploit Date Affected Version
High October 25, 2021 10/25/21
>= 20.0.3 < 20.0.13
>= 21.0.1 < 21.0.5
>= 22.1.1 < 22.2.0
Medium October 25, 2021 10/25/21
>= 20.0.3 < 20.0.13
>= 21.0.1 < 21.0.5
>= 22.1.1 < 22.2.0

tomedo / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
Critical October 18, 2019 10/18/19
== 1.7.3

bitwarden / server

2 vulnerabilities found
Title Severity Exploit Date Affected Version
High July 21, 2020 7/21/20
== 1.35.1
High December 12, 2019 12/12/19
<= 1.32.0

m-files / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium May 2, 2022 5/2/22
< 22.2.11051.0

nomachine / server

2 vulnerabilities found
Title Severity Exploit Date Affected Version
High December 7, 2021 12/7/21
>= 4.0.346.x < 7.7.4
High December 7, 2021 12/7/21
>= 4.0.346.x < 7.7.4
Node.js icon

@apollo / server

4 vulnerabilities found
Title Severity Exploit Date Affected Version
High February 4, 2026 2/4/26
>= 4.2.0 < 4.13.0
>= 5.0.0 < 5.4.0
Low August 30, 2023 8/30/23
< 4.9.3
Low June 16, 2023 6/16/23
>= 4.7.1 < 4.7.4
Medium November 2, 2022 11/2/22
< 4.1.0

go-vela / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
Critical November 10, 2022 11/10/22
< 0.16.0

gotify / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium December 29, 2022 12/29/22
< 2.2.2

onlyoffice / server

6 vulnerabilities found
Title Severity Exploit Date Affected Version
High January 23, 2023 1/23/23
<= 7.0.0.49
Critical January 23, 2023 1/23/23
<= 7.0.0.49
Medium January 23, 2023 1/23/23
<= 7.0.0.49
High January 23, 2023 1/23/23
<= 7.0.0.49
Medium January 23, 2023 1/23/23
<= 7.0.0.49
High January 23, 2023 1/23/23
<= 7.0.0.49

4d / server

3 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium November 30, 2023 11/30/23
== 19-r8
High June 16, 2023 6/16/23
== 18
== 18-r5
== 19
== 19-r7
== 17
High June 16, 2023 6/16/23
== 18
== 18-r5
== 19
== 19-r7
== 17
Node.js icon

@scrypted / server

2 vulnerabilities found
Title Severity Exploit Date Affected Version
High February 16, 2024 2/16/24
<= 0.56.0
Medium December 13, 2023 12/13/23
<= 0.55.0
Node.js icon

@budibase / server

2 vulnerabilities found
Title Severity Exploit Date Affected Version
High March 9, 2026 3/9/26
< 3.23.32
Critical March 1, 2024 3/1/24
< 2.20.0
Node.js icon

@trpc / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
High April 24, 2025 4/24/25
>= 11.0.0 < 11.1.1
Node.js icon

@kottster / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
High October 23, 2025 10/23/25
>= 3.2.0 < 3.3.2
Node.js icon

@saltcorn / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
Critical January 26, 2026 1/26/26
>= 1.1.1 < 1.5.0-beta.19
Node.js icon

@sync-in / server

1 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium February 20, 2026 2/20/26
< 1.9.3

tanium / server

4 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium February 9, 2026 2/9/26
>= 7.4.6 < 7.4.6.1151
>= 7.5.6 < 7.5.6.1161
>= 7.6.2 < 7.6.2.1293
>= 7.6.4 < 7.6.4.2114
Medium February 9, 2026 2/9/26
>= 7.4.6 < 7.4.6.1151
>= 7.5.6 < 7.5.6.1161
>= 7.6.2 < 7.6.2.1293
>= 7.6.4 < 7.6.4.2114
Medium February 9, 2026 2/9/26
>= 7.4.6 < 7.4.6.1154
>= 7.5.6 < 7.5.6.1164
>= 7.6.2 < 7.6.2.1303
>= 7.6.4 < 7.6.4.2124
Low January 30, 2026 1/30/26
>= 7.6.2.0 < 7.6.2.1327
>= 7.6.4.0 < 7.6.4.2160
>= 7.7.3.0 < 7.7.3.8231

Showing vulnerabilities for 27 products matching "server". Each product has independent pagination.

Frequently Asked Questions

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.