cKEV Index Launches to Prioritize Vulnerabilities Using Urgent Patch Score Methodology
CyberOK has launched the cKEV Index, an open catalog of prioritized vulnerabilities built on the Urgent Patch Score (UPS) methodology. The project responds to the widening gap between AI-accelerated vulnerability discovery and the unchanged time required for compatibility testing, change approval, and safe deployment.
Artificial intelligence now assists attackers in reconnaissance, code analysis, exploit development, and data processing. Anthropic documented two campaigns, GTG-50014 and GTG-50029, where small teams or even single operators used AI agents to analyze Android applications, craft working exploits, and compromise at least four websites. Similar capabilities are lowering the cost of 1-day exploit creation against already disclosed vulnerabilities.
Defenders face the same pressure. CyberOK researchers released the open-source rust-in-peace framework that combines multiple AI-driven techniques for finding, reproducing, and verifying vulnerabilities in open-source projects, including the Linux kernel. Microsoft cited increased AI-assisted findings as a reason for delaying the first cumulative update of Exchange Server Subscription Edition. Oracle patched 1,434 CVEs in a single quarterly update, attributing part of the volume to expanded AI-assisted detection.
The UPS model records verifiable signals—publication dates, PoC availability, weaponized exploits, and confirmed attacks—and maps them to operational phases: Radar, Watch, Track, Prepare, Urgent Patch, and Emergency/IR. Strong signals can immediately elevate priority without traversing every stage. The public cKEV Index currently shows only the two most urgent phases together with abbreviated event histories, CVSS, EPSS, and exploitation details.
Empirical modeling based on 245 vulnerabilities added to CISA KEV in 2025 demonstrated that organizations using early UPS signals completed 35–53% of required patches before the official KEV inclusion date, even under constrained patching capacity. Teams are advised to begin with inventory mapping on broad lists and reserve detailed testing for confirmed high-urgency items affecting their environment.
Related articles
CISA Adds BeyondTrust Remote Support and Fortinet Flaws to KEV Catalog Following Zero-Day Exploitation by ARMORY CASTLE
The US Cybersecurity and Infrastructure Security Agency has added two vulnerabilities affecting Fortinet and BeyondTrust products to its Known Exploited Vulnerabilities catalog. CVE-2026-102764 is an authentication bypass flaw in BeyondTrust Remote Support that allows remote attackers to manipulate appliance files without credentials due to insufficient source validation. BeyondTrust released an advisory on October 15, 2026, rating the issue 9.3 on CVSS v4.0 as Critical. Mandiant attributes the zero-day exploitation to the suspected Chinese group ARMORY CASTLE, which deployed web shells for persistence and privilege escalation in late August. The second CVE, CVE-2025-61624, also appears on the KEV list but lacks further public technical details in the current advisory. Organizations are urged to apply patches immediately to prevent further compromise.
Use-After-Free in HTTP/2 Upload Leads to Potential RCE in curl: Detailed Analysis of CVE-2026-92392
In curl 8.23.0, developers fixed a high-severity Use-After-Free vulnerability tracked as CVE-2026-92392 that could allow remote code execution during HTTP/2 uploads. The flaw stems from a dangling pointer left on an easy handle after a server resets an HTTP/2 stream, which later gets dereferenced when the multi handle closes. An attacker controlling the server can influence memory contents to hijack a function pointer and execute arbitrary code, though successful exploitation requires precise conditions including upload size, memory layout, and knowledge of the target architecture. The issue was discovered by Luna Tong at Anthropic using their OSS Scanner and reported to the curl security team on September 15. The team accelerated the release cycle by two weeks to deliver the fix while maintaining standard procedures. curl maintainers continue reducing internal handle pointers in favor of identifiers and are adding more tests and static analysis to prevent similar memory-safety errors. The vulnerability highlights ongoing risks in C-based networking code handling multiplexed protocols like HTTP/2.
Automating Asset Scanning in MaxPatrol VM via API: Part 4 on Authentication
A detailed technical guide explains how to build asset scanning automation in MaxPatrol VM using its API, starting with authentication methods. The author covers three authorization options including local account login-password, domain account credentials, and reference tokens, providing working Python examples for local accounts. Code reads secrets from an .env file and obtains a Bearer token valid for 24 hours from the Core role instance. The post details required privileges in both the Management Console and MaxPatrol 10 for tasks such as vulnerability exports, dynamic asset group management, scan task creation, and report exporting. It credits Alexey Leonov for an early GitHub script that enabled practical API usage and lists additional resources including webinars, SDK, CLI, Jira integration, and a Postman collection. All subsequent API calls rely on the generated headers containing the Bearer token.
Securing Hadoop Clusters: Removing Passwords from XML Configs with Credential Provider API and JCEKS
Hadoop configurations frequently expose sensitive credentials such as database passwords and cloud access keys in plain text within files like hive-site.xml and core-site.xml. The Credential Provider API, introduced in Hadoop 2.6, allows applications to retrieve secrets from an external JCEKS keystore instead of embedding them directly in XML. This mechanism uses conf.getPassword() to fetch decrypted values from the keystore when hadoop.security.credential.provider.path is configured. JCEKS relies on the outdated PBEWithMD5AndTripleDES algorithm, which remains vulnerable to Sweet32 attacks in theory though practical risk for small keystore files is low. Master password protection for the keystore itself is the weakest link, with options including environment variables, protected password files, or HDFS Transparent Data Encryption. Arenadata has automated credential encryption management in its ADH platform through ADCM to handle keystore creation, permission setting, and rotation across cluster nodes.