Tool profilesBased on official documentation, not tested by us

OpenVAS: a free scanner that checks your servers and apps for known weaknesses

OpenVAS is the scanner at the heart of the free Greenbone Community Edition: it runs a continuously updated feed of vulnerability tests against your systems. Based on the official README and the container guide, not tested by us: what it does, what it needs, its limits and what we could not confirm.

Type

Vulnerability scanner (part of the Greenbone Community Edition)

License and cost

GPL-2.0 for the main scanner code; free to run. Greenbone also sells Enterprise appliances and a trial, which we did not read about in detail

Reviewed

3 Nov 2026

Version

Not shown on the pages we read

Best for

Teams with servers or internal systems who want a free scan for known weaknesses and can run a small machine for it.

Watch out for

Greenbone's own container guide says it is meant for testing and learning, not production. Scan only systems you own or are allowed to test.

← All tool profilesNo. 7 / 11

In one sentence

OpenVAS is a vulnerabilityVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary scanner: it connects to your servers or network devices and runs thousands of tests to find known weaknesses, such as outdated software or a risky setting, using a feed of tests that is updated all the time. It is the scan engine of the free Greenbone Community Edition.

Who it is for

Teams with their own servers or internal systems who want to see what a scan finds, and who can run a small machine for it. It is not for a founder whose whole product sits on a hosted service, where the provider handles the servers. As with Wazuh, we cover it as analysis only.

What the documentation says

Everything below comes from the scanner's README and Greenbone's container guide, read on 2 November 2026.

  • What it is: the README calls it a full-featured scan engine that runs a continuously updated and extended feed of vulnerability tests. It is the scanner part of the Greenbone Community Edition and is also used in Greenbone's Enterprise appliances.
  • Code: the main scanner is written in C and built with CMake. A newer Rust implementation is also in the repository, which the README says aims to replace the current scanner stack; for now it still uses the C scanner as its engine.
  • Licences: the C module is GPL-2.0-only, with some files GPL-2.0-or-later. The Rust part is GPL-2.0-or-later with an OpenSSL exception.
  • Ways to get it: build from source, or use a prebuilt Docker image from the GitHub container registry. The README says Greenbone's containerised Community Edition is still under development.
  • Running the full edition in containers: the container guide lists Docker or podman, a shell and curl, on Debian stable, Ubuntu 24.04 LTS, Fedora 35/36 or CentOS 9 Stream. Hardware: a minimum of 2 CPU cores, 4 GB of memory and 20 GB of storage, and a recommended 4 cores, 8 GB and 60 GB.
  • Steps in the guide: install Docker, download the compose file, pull the images, start the services, set a new admin password, and open the web interface once the feed data has loaded. The web interface is served on the local machine only (127.0.0.1) over HTTPSHTTPS The secure version of the web address protocol: it encrypts what travels between a visitor and your site and checks that the site is the real one. Tap again to open the glossary with a self-signed certificate.
  • Free and paid: the README mentions an Enterprise trial, a prepared virtual machine and Enterprise appliances. It does not give a full list of which features or feeds are free or paid.
  • Signed releases: release files are signed with the Greenbone Community Feed integrity key.

The good

  • Free, open source, and a well-known scan engine with a continuously updated test feed.
  • A containerised route with a clear list of requirements and steps.
  • The web interface listens only on the local machine by default.
  • Signed releases.

The limits it admits

  • The container guide is "meant for testing and learning" and "not intended for production setups".
  • The containerised Community Edition is, per the README, still under development.
  • A default admin account exists and its password must be changed straight away.
  • The guide gives no time for the feed to load. It only says to wait until it has.

When not to use it

  • To scan systems you do not own or have no permission to test. Scanning someone else's systems can be illegal.
  • If you think a clean scan means you are safe. It means no known weakness matched.
  • If you want a quick check of a single website or app: this is a heavier tool, built for servers and networks.
  • As a production scanner without reading more than we did: Greenbone's own guide says not to.

What it costs you

A machine and time. The guide asks for at least 2 cores, 4 GB of memory and 20 GB of storage, and recommends more. After setup the work is reading the findings, working out which matter, fixing them and scanning again. We found no figures for how long a scan takes or how much the first feed load takes.

Typical setup mistakes

  • Leaving the default admin password. The guide says to change it at once.
  • Opening the web interface to the network without thinking. By default it only listens locally.
  • Scanning without permission or at the wrong time. Scans can load systems. This is general practice, not a quote from the docs.
  • Reading the report once. Findings change as the feed grows, so scan again after fixing and on a schedule.
  • Treating the findings as a to-do list with no priorities. Start with what is exposed to the internet. This is our advice.

How to check that it works

Official documentation and our approach, not something we ran: in a test virtual machine you own, with fake data and an old, known-weak setup, run a scan and check that it reports a weakness you know is there. Never scan real systems without permission.

Where to start

We did not test the tool, and it needs a server or a virtual machine, so we offer no tutorial for now. Start with the container guide: https://greenbone.github.io/docs/latest/22.4/container/index.html

What we could not confirm

We did not install or run OpenVAS. We read the scanner's README and the container guide, not the installation file, the Community Edition documentation as a whole, or the Enterprise offer. We do not know how long the feed takes to load or a scan to run, how many false alarms it gives, or how it compares with its commercial edition. The README showed no release number. We have not compared OpenVAS with other vulnerability scanners.

Glossary: vulnerability, CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary, patchPatch (security update) A fix released by the maker of a piece of software to close a flaw or a bug. Tap again to open the glossary, exposure scanner. Our free exposure checks live in Tools. Runbook 01, security check.

More free tools

Other profiles in this section.

Sources

Follow us

New profiles and security news: YouTube (@safet2ship) and Instagram (@safet2ship).

YouTube channel · Instagram

Get the free runbooks

One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

Send me the runbooks