[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f9Rih4IGH9UvwrvjtoBqJC5RbplLD-11SrXiCHYhGOIM":3},{"article":4,"iocs":42,"watch_terms":43,"solutions":44,"lesson":118},{"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":24,"category":25,"article_tags":29},"122bb24c-564d-481b-8794-d89465b43f66","OpenSSH Issues Emergency Fix for Flaw Letting Long Passwords Bypass SSH Auth on Alpine Linux","openssh-issues-emergency-fix-for-flaw-letting-long-passwords-bypass-ssh-auth-on-90a9e7","Attackers can log in to accounts that have no password, such as SSH key-only accounts, on some Alpine Linux servers running the standard openssh-server package. They need network access to the server, an account name, and a password between 257 and 1,024 bytes long. OpenSSH, which rates the flaw critical, released version 10.6p2 today to block it. Alpine has published fixed packages for every","A critical vulnerability in OpenSSH, rated as such by the OpenSSH project itself, allowed attackers to bypass SSH authentication on certain Alpine Linux servers. The flaw enabled logins to accounts without passwords, including SSH key-only accounts, provided the attacker had network access, an account name, and a specially crafted password between 257 and 1,024 bytes long. OpenSSH has released version 10.6p2 to address this issue, and Alpine Linux has published updated packages.","OpenSSH releases emergency fix for critical flaw allowing long passwords to bypass SSH auth on Alpine Linux.","https:\u002F\u002Fthehackernews.com\u002F2026\u002F11\u002Fopenssh-issues-emergency-fix-for-flaw.html","https:\u002F\u002Fblogger.googleusercontent.com\u002Fimg\u002Fb\u002FR29vZ2xl\u002FAVvXsEieaHvS5baW_XG1eAsBsoSp9qRzV179f0WwXoj9k6rUeX4Qa4sxpi3hvpGkgkYNMPzZQH0mvvVAoTooEAgl1G3SyFksmhqNEbDEIEWM83RH47u8qvNyIYclA7z7GUdPJGx8WfJd556iCvvtvsitAYp9M-T46OvuwkaSWwnyhlynEpYax2qyTCACsPbtQLw\u002Fs1600\u002Fssh-linux.jpg","2026-11-05T16:42:46+00:00","2026-11-05T22:00:35.959778+00:00",8,[17,20,22],{"name":18,"type":19},"OpenSSH","product",{"name":21,"type":19},"openssh-server",{"name":23,"type":19},"Alpine Linux","80544778-fabb-4dcd-aa35-17492e5dcf4f",{"id":24,"icon":26,"name":27,"slug":28},null,"Vulnerabilities","vulnerabilities",[30,32,37],{"category":31},{"id":24,"icon":26,"name":27,"slug":28},{"category":33},{"id":34,"icon":26,"name":35,"slug":36},"89f78b1c-3503-45a1-9fc7-e23d2ce1c6d5","Malware","malware",{"category":38},{"id":39,"icon":26,"name":40,"slug":41},"ade75414-7914-4e23-a450-48b64546ee70","Open Source","open-source",[],[18,21,23],{"controls":45,"vendors":117},[46,75,103],{"slug":47,"name":48,"problem":49,"products":50},"vulnerability-management","Vulnerability scanning and prioritisation","You know which systems are vulnerable, and which ones to fix first.",[51,59,67],{"vendor_slug":52,"vendor_name":53,"vendor_logo":54,"product_slug":55,"product_name":56,"url":57,"description":58},"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":60,"vendor_name":61,"vendor_logo":62,"product_slug":63,"product_name":64,"url":65,"description":66},"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.",{"vendor_slug":68,"vendor_name":69,"vendor_logo":70,"product_slug":71,"product_name":72,"url":73,"description":74},"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.",{"slug":76,"name":77,"problem":78,"products":79},"patch-management","Automated patch management","Known holes get closed in days, not months.",[80,88,95],{"vendor_slug":81,"vendor_name":82,"vendor_logo":83,"product_slug":84,"product_name":85,"url":86,"description":87},"action1","Action1","\u002Fvendor-logos\u002Faction1.png","action1-patch-management","Action1 Patch Management","https:\u002F\u002Fwww.action1.com\u002F","Cloud-native patch management for Windows, macOS and third-party applications.",{"vendor_slug":89,"vendor_name":90,"vendor_logo":91,"product_slug":76,"product_name":92,"url":93,"description":94},"qualys","Qualys","\u002Fvendor-logos\u002Fqualys.png","Qualys Patch Management","https:\u002F\u002Fwww.qualys.com\u002Fapps\u002Fpatch-management\u002F","Patch deployment for operating systems and third-party applications, linked to vulnerability findings.",{"vendor_slug":96,"vendor_name":97,"vendor_logo":98,"product_slug":99,"product_name":100,"url":101,"description":102},"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.",{"slug":104,"name":105,"problem":106,"products":107},"endpoint-management","Device management (MDM and UEM)","Every company laptop and phone is known, encrypted, locked down and up to date.",[108,109],{"vendor_slug":96,"vendor_name":97,"vendor_logo":98,"product_slug":99,"product_name":100,"url":101,"description":102},{"vendor_slug":110,"vendor_name":111,"vendor_logo":112,"product_slug":113,"product_name":114,"url":115,"description":116},"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":119,"title":120,"body":121,"framework_refs":122,"framework_notes":130},"openssh-auth-bypass-on-alpine-linux-highlights-critical-patching-urgency","OpenSSH Auth Bypass on Alpine Linux Highlights Critical Patching Urgency","A critical flaw in OpenSSH allowed attackers to completely bypass SSH authentication on Alpine Linux systems, including accounts configured for key-only access, simply by supplying a specially crafted long password. This means that even security-hardened configurations — where passwords should not matter — were rendered ineffective by a single unpatched vulnerability. The root cause lies in inadequate patch management practices; organizations running affected versions of OpenSSH on Alpine Linux were exposed until they applied the emergency fix in version 10.6p2. This incident underscores how a single unpatched component in a widely-used remote access tool can nullify multiple layers of security controls, making timely patching of internet-facing services non-negotiable.",[123,124,125,126,127,128,129],"CIS Control 7: Continuous Vulnerability Management","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","OWASP A06:2021 Vulnerable and Outdated Components","NIS2 Article 21(2)(b)","CIS Control 17: Incident Response Management",{"NIS2 Article 21(2)(b)":131,"NIST SP 800-53 SI-2: Flaw Remediation":132,"CIS Control 17: Incident Response Management":133,"OWASP A06:2021 Vulnerable and Outdated Components":134,"CIS Control 7: Continuous Vulnerability Management":135,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":136,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":137},"NIS2 requires essential and important entities to implement incident handling and vulnerability management practices; failure to patch a critical SSH flaw on internet-facing systems would constitute a breach of these baseline security obligations.","SI-2 requires organizations to identify, report, and correct information system flaws on defined timelines; a formal flaw remediation process would have ensured the OpenSSH emergency patch was applied promptly across all affected systems.","An established incident response process with defined procedures for critical vulnerability disclosures would have enabled organizations to rapidly triage, communicate, and remediate this emergency OpenSSH flaw across their environment.","The incident is a direct example of A06, where running an outdated or unpatched version of a critical component (OpenSSH) on Alpine Linux exposed systems to complete authentication bypass.","Regular, automated vulnerability scanning tied to patching SLAs would have identified the vulnerable OpenSSH version and triggered urgent remediation before attackers could exploit the authentication bypass.","A.8.8 mandates timely identification and remediation of technical vulnerabilities in software; applying this control would have required organizations to assess and patch the critical OpenSSH flaw upon disclosure.","This control requires that authentication mechanisms be reliably enforced; the vulnerability directly subverted SSH authentication, exposing a failure to protect the integrity of access control mechanisms through up-to-date software."]