[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fhiPT2hpLPFHV0ofIRk1FclvGwhLcKR5271Zxe_GLgPE":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":44},"6ea7653f-e55d-4032-b680-a1e74cc9ff4c","ai-uncovers-critical-nginx-flaws-hiding-since-2015-225m-sites-at-risk","762aeb6d-14ad-45ca-9d7e-ac73136d6064","AI Uncovers Critical NGINX Flaws Hiding Since 2015 — 225M Sites at Risk","AI-assisted research exposed ten vulnerabilities in NGINX, two of which carry a CVSS score of 9.2 and enable remote code execution on servers with HTTP\u002F2 enabled — a configuration common across millions of deployments. These flaws existed undetected for nearly a decade, underscoring how legacy code in widely adopted open-source software can harbour critical risks that traditional manual review misses. The incident highlights the accelerating threat landscape: if AI can find these bugs defensively, adversaries can use the same tools offensively. Organizations running internet-facing NGINX instances must treat emergency patching as a core operational capability, not an exception. Waiting for routine patch cycles is no longer acceptable when a single unpatched server can expose an entire infrastructure.","**Immediate actions:**\n- Apply F5's emergency patches for NGINX immediately, prioritising any internet-facing instances with HTTP\u002F2 enabled\n- Audit your asset inventory to identify every NGINX deployment, including those embedded in reverse proxies, load balancers, and containerised workloads\n- Disable HTTP\u002F2 on NGINX instances that cannot be patched immediately as a temporary risk-reduction measure\n\n**Long-term improvements:**\n- Establish a formal emergency patching procedure with defined SLAs for critical (CVSS 9.0+) vulnerabilities that bypasses normal change-control timelines\n- Maintain a continuously updated software bill of materials (SBOM) so open-source components like NGINX are tracked and alerted on when new CVEs are published\n- Integrate automated vulnerability scanning into CI\u002FCD pipelines so newly deployed images are checked against known CVEs before reaching production\n\n**Detection measures:**\n- Deploy web application firewall (WAF) rules targeting HTTP\u002F2 exploitation patterns as a compensating control while patches are applied\n- Monitor NGINX access and error logs for anomalous HTTP\u002F2 request patterns that may indicate exploitation attempts\n- Subscribe to vendor security advisories and threat-intelligence feeds so zero-day and emergency disclosures trigger immediate internal alerts",[12,13,14,15,16],"CIS Control 2: Inventory and Control of Software Assets (v8)","CIS Control 7: Continuous Vulnerability Management (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIS2 Article 21(2)(e)","NIST CSF 2.0 RS.MI-2: Incident Mitigation",{"NIS2 Article 21(2)(e)":18,"NIST SP 800-53 SI-2: Flaw Remediation":19,"NIST CSF 2.0 RS.MI-2: Incident Mitigation":20,"CIS Control 7: Continuous Vulnerability Management (v8)":21,"CIS Control 2: Inventory and Control of Software Assets (v8)":22},"This point requires security in acquisition, development and maintenance including vulnerability handling and disclosure, meaning operators of critical services must have processes to respond to exactly this kind of emergency open-source vulnerability disclosure.","SI-2 requires organisations to identify, report, and correct information system flaws within defined timeframes, directly addressing the need for an emergency patching process for critical NGINX vulnerabilities.","RS.MI-2 asks organisations to mitigate the effects of incidents, which maps to the need for immediate compensating controls — such as disabling HTTP\u002F2 or applying WAF rules — while emergency patches are being rolled out.","CIS Control 7 mandates continuous scanning and prioritised remediation of vulnerabilities, which would have driven immediate action when these critical CVSS 9.2 flaws were disclosed rather than leaving servers unpatched.","CIS Control 2 requires organisations to maintain an inventory of all software, which would have ensured every NGINX instance — including those buried in third-party appliances — was known and eligible for the emergency patch.","published","2026-11-18T22:20:22.828773+00:00","2026-11-18T22:20:22.809+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.theregister.com\u002Fsecurity\u002F2026\u002F11\u002F18\u002Fai-found-more-critical-bugs-in-another-widely-used-technology-running-225m-websites\u002F5310887","ai-found-more-critical-bugs-in-another-widely-used-technology-running-225m-websi-8f2f32","AI found more critical bugs in another widely used technology running 225M websites",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"af7fce9e-1ce8-4156-93bc-09dcfbfdf29d","Patch Management","patch-management","Unpatched vulnerabilities, delayed updates","#ef4444",[],[45,48,51],{"slug":34,"name":46,"problem":47},"Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",{"slug":40,"name":49,"problem":50},"Automated patch management","Known holes get closed in days, not months.",{"slug":52,"name":53,"problem":54},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them."]