# Unauthenticated remote code execution in Nginx

**URL:** <https://forum.xojo.com/t/unauthenticated-remote-code-execution-in-nginx/89236>\
**Category:** Web\
**Created:** [November 18, 2026, 10:14pm UTC](https://forum.xojo.com/t/unauthenticated-remote-code-execution-in-nginx/89236 "2026-11-18T22:14:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Derek\_Traxler](https://forum.xojo.com/letter_avatar_proxy/v4/letter/d/eb9ed0/32.png) [@Derek\_Traxler](https://forum.xojo.com/u/Derek_Traxler)\
**Post date:** [November 18, 2026, 10:14pm UTC](https://forum.xojo.com/t/unauthenticated-remote-code-execution-in-nginx/89236/1 "2026-11-18T22:14:39Z")

</div>

Heads up for anyone running a Xojo Web app behind Nginx: Looks like HTTP2 has an exploit that could effect xojo apps (Not a problem with Xojo but Nginx).

Lifeboat has had a fancy checkbox to turn off HTTP2. Thanks Tim for the great software! That took a lot of stress out of my day!

To check manually for HTTP2 on linux, you can run:

```auto
sudo nginx -T 2>/dev/null | grep -E 'http2|listen .*443'

```

Anyways, hope this helps someone and might want to keep an eye on security news moving forward.

---

<div class="post-metadata">

**Author:** ![Thom\_McGrath](https://forum.xojo.com/user_avatar/forum.xojo.com/thom_mcgrath/32/192_2.png) [@Thom\_McGrath](https://forum.xojo.com/u/Thom_McGrath)\
**Post date:** [November 18, 2026, 10:23pm UTC](https://forum.xojo.com/t/unauthenticated-remote-code-execution-in-nginx/89236/2 "2026-11-18T22:23:34Z")

</div>

Updating nginx is a good option too.
