> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/security/vulnerability-management.md).

# Vulnerability Management

Reviewed on **16 October 2026**.

## Known CVEs

A public search of [CVE.org](https://www.cve.org/), [NVD](https://nvd.nist.gov/) and [Tenable Research Advisories](https://www.tenable.com/security/research) did not identify a DocBits-named advisory on the review date. This is not proof that the application or its dependencies have no vulnerabilities. These sources do not replace an assessment of the deployed versions and the current vulnerability register. A definitive answer about open CVEs requires that assessment from FELLOWPRO.

## Assessment and remediation

The reports linked on [Certifications](https://docs.docbits.com/overview-and-basics/architecture/certifications.md) provide the following evidence:

* The SOC 2 Type II report issued in 2026 covers **1 October 2024–30 September 2025**. It describes periodic internal vulnerability scans and **at least annual third-party network vulnerability assessments and penetration tests**, with findings followed to closure.
* The ISO 27001 surveillance report records review of a VA/PT report dated **30 October 2025**, with the assessed vulnerabilities closed. This does not establish the date or results of every later test.
* The GDPR audit describes periodic product vulnerability assessments and prompt remediation of critical vulnerabilities.
* The SOC report describes testing OS/network patches for stability and availability before production, regular patching and action when critical events occur. It does not establish a numeric remediation deadline for every severity.

Request the current test scope, report, outstanding findings and contractual remediation targets from **<compliance@fellowpro.com>**. An audit's historical findings are not a current vulnerability scan.

## Updates and reporting

The [Release Lifecycle Strategy](https://docs.docbits.com/overview-and-basics/docbits-release-lifecycle-strategy.md) gives indicative planning intervals: roughly 3–4 months for major/minor releases and approximately monthly or somewhat longer for VESTA hotfixes. NOVA stabilization fixes depend on the release. These are planning estimates, not security remediation deadlines. QA and sandbox acceptance testing form part of the release process.

A public bug-bounty program, reward terms and authorized testing scope were not established by the reviewed material. Confirm those terms with FELLOWPRO before describing a program as available. Security reports and requests for penetration-test summaries can be directed to **<compliance@fellowpro.com>**; this contact does not itself grant permission to test production systems.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.docbits.com/security/vulnerability-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
