# NGINX vulnerabilities: Kinsta patch and mitigation status

**URL:** <https://community.kinsta.com/t/nginx-vulnerabilities-kinsta-patch-and-mitigation-status/8697>\
**Category:** Questions\
**Created:** [November 20, 2026, 1:53pm UTC](https://community.kinsta.com/t/nginx-vulnerabilities-kinsta-patch-and-mitigation-status/8697 "2026-11-20T13:53:41Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yuki.k](https://avatars.discourse-cdn.com/v4/letter/y/f07891/32.png) [@Yuki.k](https://community.kinsta.com/u/Yuki.k)\
**Post date:** [November 20, 2026, 1:53pm UTC](https://community.kinsta.com/t/nginx-vulnerabilities-kinsta-patch-and-mitigation-status/8697/1 "2026-11-20T13:53:41Z")

</div>

Hello Kinsta community,

We host a WordPress site on Kinsta and are reviewing the recent NGINX vulnerabilities: CVE-2026-123007, CVE-2026-123633, and CVE-2026-118899.

Has Kinsta shared an update on whether the fixes have been deployed to production and staging environments? If not, is there an estimated timeline?

While waiting for the fixes or confirmation, what temporary protections are available? In particular:

- Is HTTP/2 enabled between Cloudflare and the origin NGINX, and can it be disabled if needed?
- Does suspending an environment prevent traffic from reaching the affected NGINX, including via direct origin access?
- What protection is available for CVE-2026-118899, which is separate from the HTTP/2 issues?

We have also contacted Kinsta support and are waiting for a response. Any official update or information would be appreciated. Thank you!

---

<div class="post-metadata">

**Author:** ![VladimirM](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/vladimirm/32/2786_2.png) [@VladimirM](https://community.kinsta.com/u/VladimirM)\
**Post date:** [November 20, 2026, 1:58pm UTC](https://community.kinsta.com/t/nginx-vulnerabilities-kinsta-patch-and-mitigation-status/8697/2 "2026-11-20T13:58:43Z")

</div>

Hello @Yuki.k 👋

Thank you for reaching out.

All of these have been patched. In general, there’s no reason to worry about disclosed vulnerabilities. We have a team monitoring for these continuously and applying patches as soon as they are available, as we’ve always done.

To answer your questions:

- Is HTTP/2 enabled between Cloudflare and the origin NGINX, and can it be disabled if needed?  
Yes, Kinsta supports HTTP/2 but it cannot be disabled per container, also it’s not needed as we’ve patched this.

- Does suspending an environment prevent traffic from reaching the affected NGINX, including via direct origin access? Yes it does, but again it’s not needed.

- What protection is available for CVE-2026-118899, which is separate from the HTTP/2 issues? The patched NGINX version which we already deployed protects against this vulnerability.
