⚡Megatron LLM Hub
←返回搜索
Website

CISA 10 月新增的 5 个 KEV 全是十年前旧漏洞,至今仍在被利用。

说明补丁管理不足以拦截入侵,需对已知暴露面做持续验证。
cve漏洞管理报告
Oct 29, 2026 Why Decade-Old CVEs Are Still Being Used to Breach Networks in 2026 CISA’s latest KEV additions show that patch management alone can’t catch what continuous exposure validation would. Summary On October 8, 2026, CISA added five vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog. None are new disclosures and some date back to 2015. Patches have existed for all five vulnerabilities for years, and attackers are still exploiting them today. In many cases, the likely reason is that organizations don’t know they’re still exposed. Point-in-time vulnerability scans can create a false sense of coverage. A vulnerability that looks patched may still be reachable, misconfigured, or reintroduced through rollbacks, shadow IT, M&A, or third-party assets. CISA’s new federal remediation directive (BOD 26-04) ties KEV status to firm deadlines, which raises the cost of not knowing what you’re exposed to. Continuous threat exposure management (CTEM) helps close that gap, prioritizing exploitability and validating defensive measures on an ongoing basis instead of waiting for the next audit cycle. Author: Francisco Najera, Sales Engineering Manager Continuous threat exposure management (CTEM) is a security program model that continuously scopes, discovers, prioritizes, validates, and remediates an organization’s real-world exposure, rather than relying on periodic point-in-time scans. CISA’s newest Known Exploited Vulnerabilities (KEV) additions are a good example of why that approach matters. On October 8, 2026, CISA added five vulnerabilities to the KEV catalog. None of them are new. The oldest, ISC BIND and ProFTPD, were first disclosed in 2015—that’s eleven years ago. The newest in this group is in Strapi and goes back to 2023. Patches have existed for all five for years. Even so, attackers are exploiting them now, and in production. This looks less like a patching failure and more like a visibility failure. Organizations don’t get breached through a vulnerability with a three-year-old patch because the fix doesn’t exist. It happens because the vulnerable system was never on anyone’s radar or because no one confirmed that the fix was correctly applied. This is exactly where CTEM helps. By testing and validating your compensating controls on a continuous basis, you can confirm that even if a system remains vulnerable, your defenses will disrupt the attack and limit the impact. Which Vulnerabilities Did CISA Add to the KEV Catalog in October 2026? CISA confirmed active exploitation for all five of the KEV entries: Strapi, CVE-2023-22894 : cleartext storage of sensitive information ONLYOFFICE Docs Server, CVE-2021-3199 : path traversal Apache Struts, CVE-2016-3081 : command injection ISC BIND, CVE-2015-5477 : data processing errors ProFTPD, CVE-2015-3306 : improper access control The CISA KEV catalog exists for a simple reason: to help organizations prioritize which vulnerabilities to focus on based on real world exploitability vs a theoretically rank CVSS score. That makes the list useful, and a little uncomfortable. Every entry is evidence that somewhere, a patchable system stayed exposed long enough for an attacker to find it first. How Does CISA’s BOD 26-04 Change Vulnerability Remediation? This KEV update lands under a new federal remediation regime. CISA’s Binding Operational Directive 26-04 , issued in June 2026, replaces flat “patch within X days” timelines with risk-based deadlines. KEV status is one of the factors, along with internet exposure and how much control an attacker gains. Federal agencies feel that pressure directly, and for everyone else, it signals where auditors and regulators may be heading. A known, exploited, unpatched vulnerability is more than a security gap. It can also become a compliance problem. Why Do Patched Vulnerabilities Keep Getting Exploited? It’s tempting to read this KEV update as purely a patch management story. It’s not, or at least not only. Older CVEs with available fixes survive this long partly due to the sheer volume of vulnerabilities, because teams are slow to close tickets, and partly because of exposures nobody is tracking: Shadow IT and forgotten assets. A dev team spins up a Strapi instance for a project or may use collaboration tools without knowing ONLYOFFICE components are leveraged for a project. The project ends, but the systems remain online. M&A-inherited infrastructure. Acquired environments often carry years of unpatched legacy software that isn’t in the parent company’s scope on day one. Configuration drift. A patch gets applied, then a rebuild, rollback, or misconfigured image quietly brings the vulnerable version back. Third-party and vendor exposure. The vulnerable instance isn’t yours. It belongs to a partner or supplier with access to your environment. A vulnerability scan run once a quarter can’t see any of this in real time. It only tells you what was true when the scan ran, for the assets it knew to look for. How Does CTEM Close the Exposure Validation Gap? This is the gap continuous threat exposure management is meant to close. Instead of treating exposure as a quarterly checklist, CTEM treats it as an ongoing cycle: scope the attack surface, discover exposures, prioritize by real-world risk, validate whether they’re actually exploitable, and mobilize teams to fix what matters most. Validation is the step many programs skip, and it’s the step that provides the strongest defense despite the systems not being previously patched. Validation doesn’t ask, “Is this CVE present somewhere in our environment?” It asks, “Can an attacker actually reach and exploit this, and where can they go next?” That’s the difference between a vulnerability report and a prioritized, provable list of what’s really at risk today. This is where adversarial exposure validation comes in. It continuously and safely simulates the techniques attackers use against known exploited CVEs like these, so security teams get proof instead of an assumption that a given exposure is, or isn’t, a real path into the environment. What Should Security Leaders Do About These KEV Additions Right Now? Search your asset inventory by product name. Lookout for Shadow IT and demand the same from third parties. Search for Strapi, ONLYOFFICE Docs Server, Apache Struts, ISC BIND, and ProFTPD, not just the CVE IDs. Verify, don’t assume. Confirm the patch was actually applied on the running instance, not just closed in a ticketing system. Prioritize internet-facing systems first. That’s where CISA and attackers are both looking. Shift from periodic scanning to continuous validation. A scan tells you a vulnerability exists. Validation tells you whether it’s actually exploitable in your environment. To see how the SafeBreach CTEM platform continuously validates exposure against known exploited vulnerabilities, including the ones already on CISA’s KEV catalog, across your real environment, schedule a demo . About the Author Francisco Najera , is a Sales Engineering Manager at SafeBreach, the leader in enterprise-grade exposure validation. With over 25 years of technical experience, Francisco works closely with enterprise leaders across major industries, helping their teams validate their defenses and mature their CTEM programs. Frequently Asked Questions What is the CISA Known Exploited Vulnerabilities (KEV) catalog? The CISA Known Exploited Vulnerabilities (KEV) catalog is a list of CVEs that CISA has confirmed are being actively exploited in real-world attacks, not just rated as severe. Federal civilian agencies must remediate KEV entries by set deadlines. Many private-sector security teams also use it to prioritize, since every entry reflects confirmed, in-the-wild exploitation rather than theoretical risk. Why do attackers still exploit vulnerabilities that are years old? A patch existing doesn’t mean every instance got patched. Shadow IT, forgotten test servers, M&A-inherited systems, configuration drift, and third-party vendor assets can all keep long-patched CVEs reachable. Old exploits also tend to be well documented and reliable, which makes them cheap for attackers to reuse. What’s the difference between vulnerability management and exposure validation? A vulnerability scan reports whether a known CVE is present on a scanned or known asset; it is broad and a point in time. Exposure validation goes further by testing whether that vulnerability is actually exploitable, from a realistic attacker starting point, against your current environment, and given current defenses. It turns an assumption into proof, showing the potential impact of exploitation. What is continuous threat exposure management (CTEM)? Continuous threat exposure management (CTEM) is a five-stage framework (scoping, discovery, prioritization, validation, and mobilization) that treats exposure management as an ongoing cycle instead of a periodic audit. It’s designed to limit the impact of long-lived or reintroduced exposures, such as decade-old CVEs. How does CISA’s BOD 26-04 change vulnerability remediation requirements? CISA’s Binding Operational Directive 26-04 moves federal remediation away from flat, fixed-day patch timelines toward risk-based deadlines. KEV status, internet exposure, and the level of attacker control all factor in, with deadlines ranging from 3 to 60 days. For federal agencies, an unpatched KEV entry is now a compliance deadline as well as a security gap. How does SafeBreach help validate exposure to known exploited vulnerabilities? SafeBreach’s CTEM Platform uses adversarial exposure validation to continuously check whether known exploited CVEs are actually reachable and exploitable in your specific environment. Security teams get validated proof instead of an unconfirmed patch status. You Might Also Be Interested In Blog Have Frontier AI Models like Claude Mythos and GPT-5.5 Really Changed the Zero-Day Lifecycle? Read More Solution Brief SafeBreach CTEM Platform Read More Podcast Videos Podcast: BAS, APTs, AEV, and CTEM Explained: A Practical Guide to Cybersecurity Acronyms Listen Now Get the latest research and news