Last updated: August 19, 2026 at 1:47 AM UTC
All 741 Vulnerability 286 Breach 129 Threat 319 Defense 7
Tag: reverse-proxy (2 articles)Clear

Critical nginx flaw lets unauthenticated requests crash workers and may allow code execution

F5 patched a critical nginx vulnerability that lets a remote, unauthenticated attacker trigger a heap buffer overflow in the worker process with crafted HTTP requests. CVE-2026-42533 sits in nginx's script engine, the code that builds strings from configuration directives at request time, and only surfaces under a specific configuration: a regex based map whose output is referenced in a string expression after an earlier regex capture. Under that pattern the engine's two pass evaluation disagrees on buffer size. Triggering it crashes or restarts the worker, and F5 says code execution may be possible where address randomization is disabled or bypassed. Fixes shipped July 15.

Check
Check your nginx version and upgrade to 1.30.4, 1.31.3, or NGINX Plus 37.0.3.1 or later, and audit configurations for a regex map referenced after an earlier capture.
Affected
Organizations running nginx or NGINX Plus builds earlier than the July 15 fixes (CVE-2026-42533) with the vulnerable directive pattern; unauthenticated requests can crash workers and may allow code execution.
Fix
Upgrade to the fixed nginx releases, since patches for earlier nginx flaws do not cover this one, keep address space randomization enabled, and review configurations for the vulnerable map pattern.

Gitea Docker images trusted a forged header, letting anyone log in as any user

Attackers have started probing a critical flaw in Gitea's official Docker images, the self-hosted Git service used by many development teams. The images shipped a configuration that trusted the X-WEBAUTH-USER header from any source address, so with reverse-proxy login enabled, anyone who could reach the port could send that header and be authenticated as any user, no password required. Tracked as CVE-2026-20896 and rated 9.8, it was fixed in version 1.26.3 late last month, which removes the wildcard and makes reverse-proxy authentication opt-in. Sysdig reported the first exploitation attempt 13 days after disclosure, so far just reconnaissance, against some of the roughly 6,200 internet-facing Gitea instances.

Check
Check whether you run Gitea from its Docker image and on what version, review the app.ini reverse-proxy trusted-proxies setting for a wildcard, and whether the instance is internet-reachable.
Affected
Self-hosted Gitea Docker deployments on version 1.26.2 or earlier with reverse-proxy login enabled (CVE-2026-20896); an unauthenticated attacker who can reach the service can impersonate any user by forging one header.
Fix
Update Gitea to 1.26.3 or later, remove the wildcard from the reverse-proxy trusted-proxies setting, keep management interfaces off the public internet, and review logs for spoofed X-WEBAUTH-USER authentication attempts.