CVE-2026-19707
9.5CriticalPublished 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
Critical
0CVSS v4.010
- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-122
What an attacker gets
Remote attackers can execute code or cause a denial of service on the gateway. This requires the Smart Form Protection feature to be enabled and a backend to return specific multi-byte HTML character references.
Root cause
A heap-based buffer overflow occurs during the parsing of HTML responses within the Smart Form Protection module.
Affected versions
Airlock Gateway 8.5.2 and earlier, and 8.6.0.
CVSS v4.0 · CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade to Airlock Gateway version 8.5.3 or 8.6.1. If you cannot upgrade immediately, disable the Smart Form Protection feature on all affected mappings.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
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.