On the day of publication, the Patrowl CERT added check #1892 to Trending Attacks, the section dedicated to ongoing attacks. It checked every nginx asset monitored in EASM and Pentested modes, without sending an exploit. Triggering the vulnerability in production could have crashed your servers: we did not do it.
For each asset, the check follows five steps:
Identify the assets where nginx or OpenResty was detected: Server header, default error pages, technology detection.
Open a TLS connection that offers HTTP/2 and HTTP/1.1, and record the protocol chosen by the server. On HTTP ports, check whether HTTP/2 is accepted without TLS.
Confirm that nginx itself terminates HTTP/2, and not a CDN or a load balancer placed in front of it. The HTTP/2 settings sent by nginx have a signature of their own.
Read the Alt-Svc header to see whether HTTP/3 is advertised, and the mail port banners to spot the nginx mail proxy.
Compare the visible version with the fixed versions. An OpenResty version is mapped to the nginx version it is based on.
Each probe is a standard request, like the one a browser sends.
As of November 18, 2026, check #1892 is in "Potentially impacted" status for 127 customer teams, across 4,894 assets. This status means "to be checked", not "compromised".
Each affected customer also receives an Info-level vulnerability, "NGINX2Root: CVE-2026-123007 follow-up file of your assets", with an attached Excel file. The file ranks their assets and shows where to start: