CVE-2026-19707: Heap out-of-bounds write in the Smart Form Protection HTML entity decoder
A bug in the Airlock Gateway (8.5.2 and earlier, and 8.6.0) allows attacker-controlled HTML in a backend response to exploit the Smart Form Protection feature, possibly leading to a Denial of Service (DoS) or Remote Code Execution (RCE) attack against the Airlock Gateway. The issue has been fixed in Airlock Gateway version 8.5.3 and 8.6.1.
For an attack to be executable, the Airlock Gateway needs to have 'Smart Form Protection' (or the corresponding expert settings) enabled on a mapping whose backend returns a response containing certain multi-byte HTML character references. The buffer overflow then happens during the parsing of that HTML response. Such a response can come either from a malicious or compromised backend, or from an otherwise trusted backend that returns attacker-supplied HTML, e.g. an application that stores and serves plain user-provided HTML files.
Successfully exploiting the vulnerability can enable an attacker to perform a DoS attack or, in the worst case, an RCE attack against the Airlock Gateway in front of the affected backend. Compromising the functionality of the Airlock Gateway could in this way also affect the availability and protection of other well-intentioned backends deployed behind the same Gateway.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Airlock Gatewayto a version that resolves this vulnerability.Fixed in 8.5.3 - Upgrade
Upgrade
Airlock Gatewayto a version that resolves this vulnerability.Fixed in 8.6.1
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Affected deployments use Airlock Gateway 8.5.2 or earlier, or 8.6.0, and have Smart Form Protection or the corresponding expert settings enabled on a mapping. The mapped backend must return HTML containing certain multi-byte character references.
Does exploitation require a malicious backend?
No. The triggering response may come from a malicious or compromised backend, but a trusted backend is also relevant if it serves attacker-supplied HTML, such as stored user-provided HTML files.
What is the immediate mitigation if an upgrade cannot be performed?
Disable Smart Form Protection, or the corresponding expert settings, on mappings that could process backend responses containing attacker-controlled HTML. This removes the stated condition required for the vulnerable HTML parsing path.
How can I determine whether an instance is already remediated?
The issue is fixed in Airlock Gateway 8.5.3 and 8.6.1. Instances running those fixed versions are remediated for this vulnerability.