We're extremely grateful for security researchers and users that report vulnerabilities directly to Postgres.ai and the Database Lab Engine Community. All reports are thoroughly investigated by a set of community volunteers and the Postgres.ai team.

To report a security issue, please email us at [email protected] with all the details, attaching all necessary information.

• You think you have discovered a potential security vulnerability in the Database Lab Engine or related components.
• You are unsure how a vulnerability affects the Database Lab Engine.
• You think you discovered a vulnerability in another project that Database Lab Engine depends on (e.g., ZFS, Docker, etc).
• You want to report any other security risk that could potentially harm Database Lab Engine users.

• You're helping tune Database Lab Engine for security, perform some planned experiments coordinated with the maintainers.
• Your issue is not security related.

Each report is acknowledged and analyzed by the project's maintainers and the security team within 3 working days.

The reporter will be kept updated at every stage of the issue's analysis and resolution (triage -> fix -> release).

A public disclosure date is negotiated by the Postgres.ai security team and the bug submitter. We prefer to fully disclose the bug as soon as possible once user mitigation is available. It is reasonable to delay disclosure when the bug or the fix is not yet fully understood, the solution is not well-tested, or for vendor coordination. The timeframe for disclosure is from immediate (especially if it's already publicly known) to a few weeks. We expect the time-frame between a report to public disclosure to typically be in the order of 7 days. The Database Lab Engine maintainers and the security team will take the final call on setting a disclosure date.

This document has been inspired by and adapted from https://github.com/hasura/graphql-engine/blob/master/SECURITY.md.