# Broccoli2shell advisory

**URL:** <https://forum.airlock.com/t/broccoli2shell-advisory/404>\
**Category:** Misc\
**Tags:** microgateway\
**Created:** [October 28, 2026, 12:54pm UTC](https://forum.airlock.com/t/broccoli2shell-advisory/404 "2026-10-28T12:54:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![BacLuc](https://avatars.discourse-cdn.com/v4/letter/b/eb8c5e/32.png) [@BacLuc](https://forum.airlock.com/u/BacLuc)\
**Post date:** [October 28, 2026, 12:54pm UTC](https://forum.airlock.com/t/broccoli2shell-advisory/404/1 "2026-10-28T12:54:38Z")

</div>

Hi

Is the airlock microgateway affected by [https://github.com/envoyproxy/envoy/security/advisories/GHSA-3wvj-j6qm-62mr.](https://github.com/envoyproxy/envoy/security/advisories/GHSA-3wvj-j6qm-62mr) ?

Can you disclose the affected and the patched versions after the responsible disclosure?

Kind regards

---

<div class="post-metadata">

**Author:** ![lenggi](https://avatars.discourse-cdn.com/v4/letter/l/a587f6/32.png) [@lenggi](https://forum.airlock.com/u/lenggi)\
**Post date:** [October 28, 2026, 1:34pm UTC](https://forum.airlock.com/t/broccoli2shell-advisory/404/2 "2026-10-28T13:34:22Z")

</div>

Thank you for bringing this up.

As you have correctly pointed out: Envoy has fixed the issue in the versions v1.39.3, v1.38.6 and v1.37.8.

Airlock Microgateway versions 5.2.1, 5.1.7 and 5.0.10 include Envoy versions v1.39.4, v1.38.7 and v1.37.9 respectively and thus provide a fix for the issue at hand.  
Airlock Microgateway versions below 5.2.1, 5.1.7 and 5.0.10 are affected.

Note that you can also consult our [SBOM](https://docs.airlock.com/microgateway/5.2/technical-reference/software-bill-of-materials-and-license-texts/#retrieving-an-sbom) to get information on dependencies. Furthermore, the release notes on Github always inform you if a patch release containes an update of Envoy, e.g., [for 5.2.1](https://github.com/airlock/microgateway/releases#release-5.2.1)

Hope that helps.

Best regards,

Christoph

---

<div class="post-metadata">

**Author:** ![vshntea](https://avatars.discourse-cdn.com/v4/letter/v/c67d28/32.png) [@vshntea](https://forum.airlock.com/u/vshntea)\
**Post date:** [October 28, 2026, 3:09pm UTC](https://forum.airlock.com/t/broccoli2shell-advisory/404/3 "2026-10-28T15:09:41Z")

</div>

How exactly would this be exploitable in Airlock Microgateway, I don’t see where one can configure compression? In envoy this setting is found via [BackendTrafficPolicySpec](https://gateway.envoyproxy.io/v1.3/api/extension_types/#backendtrafficpolicyspec) and [ProxyPrometheusProvider](https://gateway.envoyproxy.io/v1.3/api/extension_types/#proxyprometheusprovider).

---

<div class="post-metadata">

**Author:** ![lenggi](https://avatars.discourse-cdn.com/v4/letter/l/a587f6/32.png) [@lenggi](https://forum.airlock.com/u/lenggi)\
**Post date:** [October 28, 2026, 4:20pm UTC](https://forum.airlock.com/t/broccoli2shell-advisory/404/4 "2026-10-28T16:20:50Z")

</div>

It would be exploitable if you use Microgateway’s EnvoyExtensionPolicy and configure the Envoy Decompression filter.

At least, that is our theoretical assumption. We have not conducted a PoC or similar.
