[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fHCbKlLl0U3fLv8Z0gaKzqGVEGIu3-1SS8094UJz_byY":3},{"article":4,"iocs":45,"iocs_total":62,"watch_terms":63,"solutions":64,"lesson":159},{"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":32,"category":33,"article_tags":37},"a6519b8b-f715-436e-b6ac-fd9df2c23661","10-Year-Old NGINX HTTP\u002F2 Flaw Lets Unauthenticated Attackers Execute Code on Servers","10-year-old-nginx-http-2-flaw-lets-unauthenticated-attackers-execute-code-on-ser-04e49d","A flaw in NGINX's HTTP\u002F2 support can allow an attacker to run code on servers with HTTP\u002F2 enabled, without needing to log in. The decade-old flaw, CVE-2026-123007, dubbed \"nginx2root,\" has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015. Fixed versions 1.31.9 and 1.30.7 came out today. F5, the company behind NGINX, says attackers can run code where","A decade-old flaw in NGINX's HTTP\u002F2 support, CVE-2026-123007, allows unauthenticated attackers to execute code on servers with HTTP\u002F2 enabled, especially when ASLR is disabled or bypassed. Researchers have demonstrated successful code execution, and in some tests, achieved root privileges by chaining this vulnerability with a separate Linux kernel bug. While proof-of-concept code is available, no exploitation in the wild has been reported, and the vulnerability is not yet listed on CISA's Known Exploited Vulnerabilities catalog. Fixed versions of NGINX Open Source and NGINX Plus have been released.","10-year-old NGINX HTTP\u002F2 flaw allows unauthenticated code execution.","https:\u002F\u002Fthehackernews.com\u002F2026\u002F11\u002F10-year-old-nginx-http2-flaw-lets.html","https:\u002F\u002Fblogger.googleusercontent.com\u002Fimg\u002Fb\u002FR29vZ2xl\u002FAVvXsEi7_qqPophooIauX16fMWm3KB24tzQ3Fd7rCuseCXfMkDPPGpIgmHqWvZjn_jffDqHwNWKu8Zf57QeKb4qsRFgdgisSAn0sMj59CscimR16RLXI1kspH0w7VYQgrsM_hPcePQOFL8QUyDC2p9W7AV0UjH3sW7oOvdWPWAZW6DITDvqIHaC_696e5kHTieY\u002Fs1600\u002Fnginx-rce.jpg","2026-11-18T18:31:17+00:00","2026-11-18T20:01:29.35581+00:00",9,[17,20,23,26,28,30],{"name":18,"type":19},"NGINX","product",{"name":21,"type":22},"F5","vendor",{"name":24,"type":25},"HTTP\u002F2","technology",{"name":27,"type":25},"ASLR",{"name":29,"type":19},"NGINX Plus",{"name":31,"type":19},"Docker","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":32,"icon":34,"name":35,"slug":36},null,"Vulnerabilities","vulnerabilities",[38,43],{"category":39},{"id":40,"icon":34,"name":41,"slug":42},"26b0b636-0e31-4db1-bffb-61bdf9f20a58","Supply Chain","supply-chain",{"category":44},{"id":32,"icon":34,"name":35,"slug":36},[46,50,53,56,59],{"type":47,"value":48,"context":49},"cve","CVE-2026-123634","flaw in NGINX with a proxied server name built from variables and SSI\u002Fmirror subrequest",{"type":47,"value":51,"context":52},"CVE-2026-113425","flaw in NGINX used as a mail proxy",{"type":47,"value":54,"context":55},"CVE-2026-123007","nginx2root flaw in NGINX HTTP\u002F2 support",{"type":47,"value":57,"context":58},"CVE-2026-123633","flaw in NGINX HTTP\u002F2 with requests passed to a backend server",{"type":47,"value":60,"context":61},"CVE-2026-121810","flaw in NGINX HTTP\u002F3 support",5,[21,18,29],{"controls":65,"vendors":153},[66,95,124],{"slug":67,"name":68,"problem":69,"products":70},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[71,79,87],{"vendor_slug":72,"vendor_name":73,"vendor_logo":74,"product_slug":75,"product_name":76,"url":77,"description":78},"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":80,"vendor_name":81,"vendor_logo":82,"product_slug":83,"product_name":84,"url":85,"description":86},"tenable","Tenable","\u002Fvendor-logos\u002Ftenable.png","tenable-vulnerability-management","Tenable Vulnerability Management","https:\u002F\u002Fwww.tenable.com\u002Fproducts\u002Fvulnerability-management","Cloud-based vulnerability scanning and prioritisation, built on Nessus.",{"vendor_slug":88,"vendor_name":89,"vendor_logo":90,"product_slug":91,"product_name":92,"url":93,"description":94},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","vmdr","Qualys VMDR","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fvulnerability-management-detection-response\u002F","Vulnerability management, detection and response with risk-based prioritisation.",{"slug":96,"name":97,"problem":98,"products":99},"patch-management","Automated patch management","Known holes get closed in days, not months.",[100,108,116],{"vendor_slug":101,"vendor_name":102,"vendor_logo":103,"product_slug":104,"product_name":105,"url":106,"description":107},"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":109,"vendor_name":110,"vendor_logo":111,"product_slug":112,"product_name":113,"url":114,"description":115},"ivanti","Ivanti","\u002Fvendor-logos\u002Fivanti.png","neurons-patch-management","Ivanti Neurons for Patch Management","https:\u002F\u002Fwww.ivanti.com\u002Fproducts\u002Fivanti-neurons-for-patch-management","Risk-based patch management for operating systems and third-party applications.",{"vendor_slug":117,"vendor_name":118,"vendor_logo":119,"product_slug":120,"product_name":121,"url":122,"description":123},"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.",{"slug":125,"name":126,"problem":127,"products":128},"endpoint-detection-response","Endpoint detection and response (EDR and XDR)","Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.",[129,137,145],{"vendor_slug":130,"vendor_name":131,"vendor_logo":132,"product_slug":133,"product_name":134,"url":135,"description":136},"crowdstrike","CrowdStrike","\u002Fvendor-logos\u002Fcrowdstrike.png","falcon-insight-xdr","Falcon Insight XDR","https:\u002F\u002Fwww.crowdstrike.com\u002Fen-us\u002Fplatform\u002Fendpoint-security\u002Ffalcon-insight-xdr\u002F","Endpoint detection and response with extended detection across other security tools.",{"vendor_slug":138,"vendor_name":139,"vendor_logo":140,"product_slug":141,"product_name":142,"url":143,"description":144},"sophos","Sophos","\u002Fvendor-logos\u002Fsophos.png","sophos-endpoint","Sophos Endpoint","https:\u002F\u002Fwww.sophos.com\u002Fen-us\u002Fproducts\u002Fendpoint-security","Endpoint protection with Intercept X anti-ransomware technology and EDR.",{"vendor_slug":146,"vendor_name":147,"vendor_logo":148,"product_slug":149,"product_name":150,"url":151,"description":152},"bitdefender","Bitdefender","\u002Fvendor-logos\u002Fbitdefender.png","gravityzone","GravityZone","https:\u002F\u002Fwww.bitdefender.com\u002Fen-us\u002Fbusiness\u002Fgravityzone-platform\u002F","Endpoint protection, detection and response platform.",[154],{"slug":155,"name":21,"logo_path":156,"roles":157},"f5","\u002Fvendor-logos\u002Ff5.png",[158],"affected",{"slug":160,"title":161,"body":162,"framework_refs":163,"framework_notes":169},"decade-old-nginx-http2-flaw-enables-unauthenticated-remote-code-execution","Decade-Old NGINX HTTP\u002F2 Flaw Enables Unauthenticated Remote Code Execution","A ten-year-old vulnerability in NGINX's HTTP\u002F2 implementation (CVE-2026-123007) allows unauthenticated attackers to execute arbitrary code on exposed servers, with the risk escalating to root-level access when chained with a Linux kernel bug. The flaw went undetected for a decade, highlighting how legacy code paths in widely deployed infrastructure can harbor critical vulnerabilities long after introduction. The availability of public proof-of-concept code significantly lowers the bar for exploitation, meaning the window between patch release and active exploitation is narrow. Organizations running HTTP\u002F2 on NGINX without a disciplined patch cycle are exposed to full server compromise with no authentication required.",[164,165,166,167,168],"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)":170,"NIST SP 800-53 SI-2: Flaw Remediation":171,"CIS Control 7: Continuous Vulnerability Management (v8)":172,"CIS Control 2: Inventory and Control of Software Assets (v8)":173,"NIST CSF 2.0 RS.MI-3: Newly identified vulnerabilities are mitigated or documented as accepted risks":174},"Article 21(2)(e) mandates security in acquisition, development, and maintenance including vulnerability handling; operators of essential or important services must have processes to promptly address vulnerabilities like this one in third-party components.","SI-2 requires organizations to identify, report, and correct information system flaws in a timely manner; applying this control would have ensured the NGINX fix was tested and deployed promptly after the vendor released patched versions.","CIS Control 7 requires organizations to continuously assess and remediate vulnerabilities; a mature vulnerability management program would have identified the unpatched NGINX flaw and triggered timely remediation before public exploit code became available.","CIS Control 2 requires maintaining an accurate inventory of all software in use; knowing every instance of NGINX deployed across the environment is a prerequisite for rapidly applying the patch once the vulnerability was disclosed.","This category directly addresses the need to act on newly disclosed vulnerabilities; organizations without a defined response process for new CVEs would delay patching and remain exposed to the now-public proof-of-concept exploit."]