[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fAjhJnwmnrLahTXiWpvSnSWvCJ-LB6So4fZCSKnNmPDs":3},{"article":4,"iocs":38,"iocs_total":55,"watch_terms":56,"solutions":57,"lesson":158},{"id":5,"title":6,"slug":7,"summary":8,"ai_summary":9,"brief":10,"url":11,"image_url":12,"published_at":13,"ingested_at":14,"relevance_score":15,"entities":16,"category_id":25,"category":26,"article_tags":30},"38eee23b-e3e9-4236-a4a0-b86c1157afd3","8.8 Million NGINX Services Still Potentially Exposed to Critical NGINX2Root Vulnerability","8-8-million-nginx-services-still-potentially-exposed-to-critical-nginx2root-vuln-7b1d2d","Around 8.8 million NGINX services may still be open to the NGINX2Root flaws. Censys live tracker counts 8,823,450 services that run an affected version and offer HTTP\u002F2. Another 441,489 services that were once exposed have since been patched or have turned HTTP\u002F2 off. NGINX2Root is a set of five memory bugs in NGINX that Xint […] The post 8.8 Million NGINX Services Still Potentially Exposed to Critical NGINX2Root Vulnerability appeared first on Cyber Security News.","Approximately 8.8 million NGINX services remain vulnerable to the NGINX2Root flaws, a set of five memory bugs disclosed on November 18, 2026. The most severe, CVE-2026-123007, affects versions from 1.9.5 to 1.31.8 and can allow unauthenticated remote users to run commands as a worker process. While some services have been patched or disabled HTTP\u002F2, many remain exposed, particularly those using HTTP\u002F3 or mail proxy configurations.","8.8 Million NGINX Services Potentially Exposed to Critical NGINX2Root Vulnerability","https:\u002F\u002Fcybersecuritynews.com\u002Fnginx2root-vulnerability\u002F","https:\u002F\u002Fcybersecuritynews.com\u002Fwp-content\u002Fuploads\u002F2026\u002F11\u002FNGINX2Root.webp","2026-11-20T02:46:13+00:00","2026-11-20T03:00:36.158768+00:00",9,[17,20,23],{"name":18,"type":19},"NGINX","product",{"name":21,"type":22},"HTTP\u002F2","technology",{"name":24,"type":22},"HTTP\u002F3","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":25,"icon":27,"name":28,"slug":29},null,"Vulnerabilities","vulnerabilities",[31,33],{"category":32},{"id":25,"icon":27,"name":28,"slug":29},{"category":34},{"id":35,"icon":27,"name":36,"slug":37},"e7b231c8-5f79-4465-8d38-1ef13aea5a14","Threat Intelligence","threat-intelligence",[39,43,46,49,52],{"type":40,"value":41,"context":42},"cve","CVE-2026-113425","NGINX2Root vulnerability requiring the mail proxy with auth_http.",{"type":40,"value":44,"context":45},"CVE-2026-121810","NGINX2Root vulnerability requiring HTTP\u002F3 with a backend proxy.",{"type":40,"value":47,"context":48},"CVE-2026-123633","NGINX2Root vulnerability requiring HTTP\u002F2 with a backend proxy.",{"type":40,"value":50,"context":51},"CVE-2026-123007","Most serious NGINX2Root vulnerability affecting NGINX versions 1.9.5 through 1.31.8.",{"type":40,"value":53,"context":54},"CVE-2026-123634","NGINX2Root vulnerability requiring DNS lookups at request time plus subrequests.",5,[18],{"controls":58,"vendors":145},[59,88,117],{"slug":60,"name":61,"problem":62,"products":63},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[64,72,80],{"vendor_slug":65,"vendor_name":66,"vendor_logo":67,"product_slug":68,"product_name":69,"url":70,"description":71},"axonius","Axonius","\u002Fvendor-logos\u002Faxonius.png","axonius-exposures","Axonius Exposures","https:\u002F\u002Fwww.axonius.com\u002Fplatform\u002Fexposures","Brings findings from different scanners together with asset and business context, to show what matters most and track fixes to the end.",{"vendor_slug":73,"vendor_name":74,"vendor_logo":75,"product_slug":76,"product_name":77,"url":78,"description":79},"holm-security","Holm Security","\u002Fvendor-logos\u002Fholm-security.png","holm-security-platform","Holm Security Platform","https:\u002F\u002Fwww.holmsecurity.com\u002F","Vulnerability scanning of systems, web applications, cloud and the external attack surface, plus phishing simulation.",{"vendor_slug":81,"vendor_name":82,"vendor_logo":83,"product_slug":84,"product_name":85,"url":86,"description":87},"rapid7","Rapid7","\u002Fvendor-logos\u002Frapid7.png","insightvm","Rapid7 Exposure Command (InsightVM)","https:\u002F\u002Fwww.rapid7.com\u002Fproducts\u002Finsightvm\u002F","Vulnerability scanning and risk-based prioritisation; InsightVM is now part of Exposure Command, alongside attack surface and cloud risk.",{"slug":89,"name":90,"problem":91,"products":92},"patch-management","Automated patch management","Known holes get closed in days, not months.",[93,101,109],{"vendor_slug":94,"vendor_name":95,"vendor_logo":96,"product_slug":97,"product_name":98,"url":99,"description":100},"microsoft","Microsoft","\u002Fvendor-logos\u002Fmicrosoft.png","intune","Microsoft Intune","https:\u002F\u002Fwww.microsoft.com\u002Fen-us\u002Fsecurity\u002Fbusiness\u002Fmicrosoft-intune","Device management for Windows, macOS, iOS and Android, including update rings and compliance policies.",{"vendor_slug":102,"vendor_name":103,"vendor_logo":104,"product_slug":105,"product_name":106,"url":107,"description":108},"ninjaone","NinjaOne","\u002Fvendor-logos\u002Fninjaone.png","ninjaone-patch-management","NinjaOne Patch Management","https:\u002F\u002Fwww.ninjaone.com\u002Fpatch-management\u002F","Automated patching of operating systems and third-party applications from the cloud.",{"vendor_slug":110,"vendor_name":111,"vendor_logo":112,"product_slug":113,"product_name":114,"url":115,"description":116},"manageengine","ManageEngine","\u002Fvendor-logos\u002Fmanageengine.png","patch-manager-plus","ManageEngine Patch Manager Plus","https:\u002F\u002Fwww.manageengine.com\u002Fpatch-management\u002F","Patch management for operating systems and third-party applications, on premises or in the cloud.",{"slug":37,"name":118,"problem":119,"products":120},"Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them.",[121,129,137],{"vendor_slug":122,"vendor_name":123,"vendor_logo":124,"product_slug":125,"product_name":126,"url":127,"description":128},"crowdstrike","CrowdStrike","\u002Fvendor-logos\u002Fcrowdstrike.png","falcon-adversary-intelligence","Falcon Adversary Intelligence","https:\u002F\u002Fwww.crowdstrike.com\u002Fen-us\u002Fplatform\u002Fthreat-intelligence\u002F","Threat intelligence on the adversaries CrowdStrike tracks, built into the Falcon platform to detect, disrupt and defend against them.",{"vendor_slug":130,"vendor_name":131,"vendor_logo":132,"product_slug":133,"product_name":134,"url":135,"description":136},"dataminr","Dataminr","\u002Fvendor-logos\u002Fdataminr.png","agentic-threat-intelligence-platform","Agentic Threat Intelligence Platform","https:\u002F\u002Fwww.dataminr.com\u002Fproducts\u002Fcyber-defense\u002Fagentic-threat-intelligence-platform\u002F","Threat intelligence platform, formerly ThreatConnect TI Ops, that collects, scores and structures intelligence and pushes it into security tools.",{"vendor_slug":138,"vendor_name":139,"vendor_logo":140,"product_slug":141,"product_name":142,"url":143,"description":144},"recorded-future","Recorded Future","\u002Fvendor-logos\u002Frecorded-future.png","recorded-future-cyber-operations","Recorded Future Cyber Operations","https:\u002F\u002Fwww.recordedfuture.com\u002Fproducts\u002Fcyber-operations","Threat intelligence built into security operations workflows, to prioritise alerts and act on threats before they arrive.",[146,152],{"slug":147,"name":148,"logo_path":149,"roles":150},"censys","Censys","\u002Fvendor-logos\u002Fcensys.png",[151],"reported_by",{"slug":153,"name":154,"logo_path":155,"roles":156},"f5","F5","\u002Fvendor-logos\u002Ff5.png",[157],"affected",{"slug":159,"title":160,"body":161,"framework_refs":162,"framework_notes":168},"88-million-nginx-servers-still-exposed-weeks-after-critical-patch-release","8.8 Million NGINX Servers Still Exposed Weeks After Critical Patch Release","Despite a patch being available, approximately 8.8 million NGINX services remain vulnerable to the NGINX2Root flaws, including a critical unauthenticated remote code execution vulnerability affecting a wide range of versions. The sheer scale of exposure weeks after disclosure highlights a systemic failure in patch management processes, particularly for internet-facing infrastructure. Organizations running HTTP\u002F3 or mail proxy configurations face heightened risk as common mitigations like disabling HTTP\u002F2 do not fully protect them. This incident underscores that critical vulnerabilities in widely deployed web servers demand immediate, prioritized patching — not passive dependency on default update cycles.",[163,164,165,166,167],"CIS Control 7: Continuous Vulnerability Management (v8)","CIS Control 2: Inventory and Control of Software Assets (v8)","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks","NIS2 Article 21(2)(e)",{"NIS2 Article 21(2)(e)":169,"NIST SP 800-53 SI-2: Flaw Remediation":170,"CIS Control 7: Continuous Vulnerability Management (v8)":171,"CIS Control 2: Inventory and Control of Software Assets (v8)":172,"NIST CSF 2.0 RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks":173},"NIS2 Article 21(2)(e) mandates security in acquisition, development and maintenance including vulnerability handling, requiring operators of essential and important services to address disclosed vulnerabilities promptly — directly applicable to the delayed patching of these critical NGINX flaws.","SI-2 requires organizations to identify, report, and correct information system flaws within defined time frames, directly addressing the failure to apply the NGINX2Root patches in a timely manner.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities — a process that would have identified unpatched NGINX instances and driven timely updates before 8.8 million services remained exposed.","CIS Control 2 requires maintaining an accurate inventory of all software in use, which is a prerequisite for knowing which NGINX versions are deployed and need patching across an organization's estate.","This category requires that once a vulnerability is disclosed, organizations act to mitigate it or formally accept the risk — the mass non-patching of NGINX indicates this process was absent or ineffective for millions of deployments."]