---
schema: 1
kind: vulnerability
title: "CVE-2026-19707, Airlock Gateway 8.5.0 to 8.5.2 and 8.6.0: attacker-controlled HTML in a backend response overflows a buffer in the Smart Form Protection feature and can cause denial of service or code execution on the gateway; fixed in 8.5.3 and 8.6.1, no exploitation reported (CVSS 4.0 9.5)"
headline: "Airlock Gateway: Smart Form Protection buffer overflow can crash or take over the gateway; update to 8.5.3 or 8.6.1"
summary: >
  Airlock (Ergon) published CVE-2026-19707 on 2026-11-18: attacker-controlled HTML in a backend response can overflow a buffer in the Smart Form Protection feature of Airlock Gateway 8.5.0 to 8.5.2 and 8.6.0, possibly causing denial of service or remote code execution against the gateway, when the feature is enabled on a mapping whose backend returns certain multi-byte HTML character references (CVSS 4.0 9.5, high attack complexity). The fix is in 8.5.3 and 8.6.1, no source reports exploitation, and Airlock says a compromised gateway could also affect the protection of the other backends behind it.
discovered_at: "2026-11-19T05:18:00Z"
updated_at: null
event_date: "2026-11-18"
run_id: 2026-11-19T0355Z-intel
priority: notable
immediate_action: null
tags: [vulnerabilities, rce, pre-auth, patch-available]
regions: [global]
sectors: [technology]
entities: ["product:airlock-gateway"]
techniques: [T1190, T1499.004]
affected_products: ["Airlock Gateway"]
cves:
  - id: CVE-2026-19707
    cvss: "9.5 (CVSS 4.0)"
    epss: null
    type: memory-corruption
    vector: zero-click
    auth: pre-auth
    status: [patch-available]
    affected: "Airlock Gateway 8.5.0 to 8.5.2 and 8.6.0 with Smart Form Protection enabled on a mapping whose backend returns certain multi-byte HTML character references"
    fixed: "8.5.3 and 8.6.1"
sources:
  - url: "https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-128505"
    publisher: "ENISA EUVD (record carrying Airlock's CNA text)"
    date: "2026-11-18"
    role: primary
  - url: "https://docs.airlock.com/gateway/latest/index/1781491741687.html"
    publisher: "Airlock Gateway documentation (changelog 8.6.1)"
    date: "2026-11-19"
    role: corroborating
  - url: "https://docs.airlock.com/gateway/8.5/index/1755485389146.html"
    publisher: "Airlock Gateway documentation (changes 8.5.2 to 8.5.3)"
    date: "2026-11-19"
    role: corroborating
  - url: "https://docs.airlock.com/gateway/latest/index/1648621032215.html"
    publisher: "Airlock Gateway documentation (Smart Form Protection)"
    date: "2026-11-19"
    role: corroborating
  - url: "https://docs.airlock.com/gateway/latest/index/1755485389142.html"
    publisher: "Airlock Gateway documentation (releases and support lifecycle)"
    date: "2026-11-19"
    role: corroborating
closed_sources: []
evidence:
  - quote: "The issue has been fixed in Airlock Gateway version 8.5.3 and 8.6.1."
    publisher: "ENISA EUVD (record carrying Airlock's CNA text)"
    source_url: "https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-128505"
  - quote: "FIX: AP-38633 Fix buffer overflow when decoding HTML entities"
    publisher: "Airlock Gateway documentation (changelog 8.6.1)"
    source_url: "https://docs.airlock.com/gateway/latest/index/1781491741687.html"
verification: single-source
sourcing_note: >
  Airlock is the CNA and the disclosing party, and the ENISA record carries its CVE text; Airlock's own advisory page (the link in the record) is a disclosure policy that lists no advisories and its customer portal asks for a login, so the corroboration is the vendor's public release notes, which list the same fix without a CVE id or a security label. The finders and any technical write-up are not named in the sources read, and the documentation pages carry no dateline, so their citations carry the retrieval date.
confidence: medium
references: []
deep_dive: false
deep_dive_category: null
org_triage: null
classification:
  reliability: A
  credibility: 2
watchlist_hit: false
actions:
  - "Move every Airlock Gateway running 8.5.0 through 8.5.2 to 8.5.3 and every one running 8.6.0 to 8.6.1, starting with gateways that have Smart Form Protection enabled on a mapping whose backend serves user-supplied HTML, because Airlock says one backend response can crash or take over the gateway that protects every backend behind it."
updates: []
migrated_from: null
---

Airlock (Ergon) published CVE-2026-19707 on 2026-11-18 as the CNA. It says attacker-controlled HTML in a backend response can exploit the Smart Form Protection feature of Airlock Gateway 8.5.2 and earlier and 8.6.0, possibly leading to a denial of service or remote code execution against the gateway, and that the issue is fixed in 8.5.3 and 8.6.1 ([ENISA EUVD, 2026-11-18](https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-128505)). The attack needs Smart Form Protection, or the corresponding expert settings, enabled on a mapping whose backend returns a response containing certain multi-byte HTML character references, and the overflow happens while the gateway parses that response; the response can come from a malicious or compromised backend or from a trusted backend that returns attacker-supplied HTML, for example an application that stores and serves user-provided HTML files ([ENISA EUVD, 2026-11-18](https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-128505)). The record scores CVSS 4.0 9.5 with high attack complexity and says that compromising the gateway could also affect the availability and protection of other backends deployed behind it ([ENISA EUVD, 2026-11-18](https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-128505)). Airlock's release notes for 8.6.1 and 8.5.3 list a fix for a buffer overflow when decoding HTML entities in the same releases, without a CVE id ([Airlock documentation, 2026-11-19](https://docs.airlock.com/gateway/latest/index/1781491741687.html); [Airlock documentation, 2026-11-19](https://docs.airlock.com/gateway/8.5/index/1755485389146.html)). Airlock's support table shows 8.5 supported until 06/2027, 8.4 past its end of support in 08/2026 and 8.3 no longer supported ([Airlock documentation, 2026-11-19](https://docs.airlock.com/gateway/latest/index/1755485389142.html)).

**Exposure:** Airlock Gateway 8.5.0 to 8.5.2 or 8.6.0 with Smart Form Protection enabled, which Airlock's documentation says requires URL encryption to be activated first, on a mapping whose backend can return attacker-supplied HTML ([ENISA EUVD, 2026-11-18](https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-128505); [Airlock documentation, 2026-11-19](https://docs.airlock.com/gateway/latest/index/1648621032215.html)). Gateways on 8.4 and older are outside support and have no listed fix.

**Detection:** the record names no indicator; gateway process crashes or restarts and unexpected child processes on the gateway, and backend responses with unusual multi-byte HTML character references, follow from the mechanism ([ENISA EUVD, 2026-11-18](https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-128505)).

**Defender takeaway:** update to 8.5.3 or 8.6.1, backends that serve user-supplied HTML behind a gateway with Smart Form Protection first; no source reports exploitation, so the order follows exposure rather than a known campaign ([ENISA EUVD, 2026-11-18](https://euvdservices.enisa.europa.eu/api/enisaid?id=EUVD-2026-128505)).
