Skip to main content
Report a suspected vulnerability in FalkorDB Enterprise privately, so a fix can ship before the details are public. This page covers how to report, what to include, and how fixes reach you.

Report privately

Email security@falkordb.com.
Do not open a public GitHub issue, discussion or pull request for a suspected vulnerability, and do not share the details publicly until a fix is available.

What to include

A support package is redacted and can be attached if it helps reproduce the issue.

What happens next

1

Acknowledgement

FalkorDB confirms that it received your report and tells you who is handling it.
2

Assessment

FalkorDB reproduces the issue, decides which versions are affected, and keeps you informed of progress.
3

Fix

The fix ships in a new FalkorDB Enterprise release. Upgrade as described in Upgrade FalkorDB Enterprise.
4

Advisory

Once the fix is available, the release’s changelog entry describes the vulnerability under Security, with the CVE identifier when one is assigned.
Response times for customers are set by your FalkorDB Enterprise agreement.

Where fixes are announced

  • The Security section of each release in the changelog.
  • The Releases page of the Enterprise Portal, which lists every published version with its release notes.

Third-party components

FalkorDB Enterprise bundles third-party software, such as KubeBlocks and the CSI snapshot controller. Report a vulnerability in one of them to its upstream project. If it affects FalkorDB Enterprise, report it to FalkorDB as well, so a fixed version can be bundled in a release. To check the images you run against vulnerability databases yourself, read the signed bill of materials each image carries. See Supply chain.