Airlock Security Advisories

Vulnerability Disclosure Policy

Last modified: May 8th, 2026

As a vendor of a security software suite, we are dedicated to keeping our software secure. We welcome security researchers to reach out and report any potential vulnerabilities discovered in our products.
 

Scope

Subject to this vulnerability disclosure policy is the security suite “Airlock Secure Access Hub” including the components

  • Airlock SaaS
  • Airlock Identity and Access Management (IAM)
  • Airlock Gateway
  • Airlock Microgateway 

deployed as self-contained application or in containerized form.
 

Vulnerability definition

We consider a vulnerability any issue with a demonstrable negative security impact on a supported component within our scope — typically allowing an attacker violate confidentiality, integrity, or availability, or to bypass a documented security control. Theoretical weaknesses without demonstrable impact, missing defense-in-depth hardening, issues depending on configurations we explicitly discourage, and vulnerabilities in third-party components where Airlock is not the upstream maintainer are evaluated case by case and may be addressed without a CVE. End-of-life versions generally receive a CVE only when the same issue also affects a supported version.
 

Reporting a vulnerability

Reports are accepted via email at security@airlock.com. We encourage you to encrypt your submission using our PGP public key. 

Please provide a detailed technical explanation of the required steps to reproduce the issue, including descriptions of any tools used for identification or exploitation. Please attach screenshots and other supporting documents. We favor reports that include proof-of-concept code demonstrating how the vulnerability can be exploited. If your submission contains exploit code or scripts, please include them in a non-executable file format.

When reporting a vulnerability, you may include contact information and preferred communication details. We may reach out to clarify elements of your report or request additional technical details.

By submitting a report to Airlock, you confirm that neither the report nor its attachments infringe on any third-party intellectual property rights. You also grant Airlock a non-exclusive, royalty-free, worldwide, perpetual license to use, reproduce, create derivative works from, and publish the report and its attachments.

Disclosure

Airlock is committed to promptly addressing vulnerabilities that could impact our customers. We will acknowledge compliant reports within five (5) business days. We will triage the report and tell you whether we have validated it, need more information, or do not consider it in scope (with reasoning). For confirmed in-scope vulnerabilities, Airlock reserves a CVE ID and shares it with you as a common reference, agrees a coordinated disclosure date with you (normally aligned with the release of a fix), and publishes the CVE record at or shortly after the corresponding advisory appears on this page.

Credit in the advisory and CVE record is offered by default.

CVE ID assignment is decided independently of bounty eligibility in any bug bounty program — a report may qualify for a CVE without qualifying for a bounty, and vice versa.

To protect users, please do not publish information about the submitted vulnerability until we have explicitly agreed to its disclosure.

If you act in good faith and in compliance with this policy, Airlock will collaborate with you to resolve the issue and will not pursue legal action related to your research.

Further information

Questions regarding this policy or the process of reporting a vulnerability may be sent to security@airlock.com. 

Information for you

-Our whitepapers-
White paper: The puzzle pieces of modern authentication

White paper: The puzzle pieces of modern authentication

Identity management is like a puzzle: you have to understand the big picture, identify the relevant pieces and put them together in the right order. This white paper shows how to do that.

 

Request white paper

Whitepaper: How to make cIAM a success

Increasing requirements for security and user-friendliness make Customer Identity and Access Management an essential. Read our whitepaper to find out how you can secure your competitive advantage with the right CIAM strategy.

 

Request whitepaper

Whitepaper: Security for cloud-native applications

You can read about how companies can ensure the security of web applications and APIs in Kubernetes in the white paper "Security for cloud-native applications", which was created in collaboration between heise and Airlock.

 

Request whitepaper

Whitepaper: Zero Trust is a journey

The ongoing digital transformation of the world is progressing and having a profound impact on our personal and professional lives in ways that were difficult to imagine just a few years ago.


This white paper discusses the effects of continuous digitalization and its impact.

Request free of charge

Off to DevSecOps

In this white paper, you will learn the most important insights into how you can implement DevSecOps successfully and efficiently, which security components are required for this and the advantages of a microgateway architecture.

 

Request free of charge

Airlock 2FA - Strong authentication. Simple.

Double security - this is what two-factor authentication offers in the field of IT security.


Find out more about strong authentication and the possibilities offered by Airlock in our white paper.

Download for free

Further whitepapers

We provide you with free white papers on these and other topics:

 

  • Successful IAM projects
  • compliance
  • Data protection (DSGVO)
  • Introduction of PSD2
  • PCI DSS requirementsPCI DSS requirements
Request free of charge