May 2026 CVE Landscape
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2008-4250 | Remote Code Execution Buffer Overflow in Microsoft Windows Server Service Microsoft Windows contains a buffer overflow in the Windows Server Service that is triggered when a specially crafted RPC request causes an overflow during path canonicalization. A remote attacker who can reach the service (historically over SMB) can send such a request and execute arbitrary code on the target system. Any Microsoft Windows system running the Server Service is affected, with exposure concentrated on legacy or unpatched machines whose RPC/SMB interface is reachable from untrusted networks. CISA added the flaw (CVE-2008-4250, the vulnerability addressed by Microsoft's 2008 MS08-067 bulletin) to its Known Exploited Vulnerabilities catalog on 2026-05-20, confirming exploitation in the wild, with no ransomware association yet documented. Its EPSS score of 98.8% (100th percentile) indicates a very high likelihood of continued exploitation over the next 30 days. Do: Confirm that every Windows host has the Server Service fix from Microsoft bulletin MS08-067 (released October 2008) or a later Windows update, prioritizing internet-facing and legacy systems that may never have been patched. Restrict inbound SMB/RPC (TCP 445) to trusted networks, disable the Server Service where it is not required, and hunt for indicators of compromise on unpatched hosts. Federal agencies must apply mitigations per vendor instructions and applicable BOD 22-01 guidance, or discontinue use of the product if mitigations are unavailable, per the KEV required action. | — | 99% | KEV |
| massMillions of Windows systems in total; likely hundreds of thousands of internet-exposed SMB hosts, many on legacy or unpatched machines | |
| CVE-2009-1537 | Null Byte Overwrite RCE in Microsoft DirectX QuickTime Parser (quartz.dll) CVE-2009-1537 is a NULL byte overwrite vulnerability in the QuickTime Movie Parser Filter inside quartz.dll, a DirectShow component of Microsoft DirectX. It is triggered when the affected DirectShow component parses a crafted QuickTime (.mov) media file, such as one opened from a website, media player, or email. A successful exploit allows a remote attacker to execute arbitrary code on the targeted system. Any Microsoft installation with the vulnerable DirectX/DirectShow component is affected, with real-world risk concentrated on systems that render untrusted QuickTime media. The flaw is long-standing (2009) but CISA added it to the Known Exploited Vulnerabilities catalog on 2026-05-20, confirming active exploitation; EPSS puts its 30-day exploitation probability at 51.2% (99th percentile), while no public PoC is known and ransomware use is unconfirmed. Do: Apply Microsoft's mitigations per vendor instructions, and follow BOD 22-01 requirements for cloud services in federal environments; ensure affected systems have the vendor's updated quartz.dll/DirectShow fix installed rather than relying on default installations. Until patched, avoid opening untrusted QuickTime (.mov) files and block or inspect .mov files delivered via email and web downloads. Treat this as a high priority given the KEV listing and elevated EPSS score, even though ransomware association is not yet confirmed. | — | 51% | KEV |
| masshundreds of millions of Windows installations (DirectX/DirectShow ships as a standard Windows component) | |
| CVE-2009-3459 | Heap-Based Buffer Overflow in Adobe Acrobat and Reader Enables RCE via PDFs Adobe Acrobat and Reader contain a heap-based buffer overflow (CWE-119) in the processing of PDF content that corrupts process memory. The flaw is triggered remotely when a user opens a specially crafted PDF file, requiring no authentication and only that the victim open or view the malicious document. Successful exploitation allows an attacker to execute arbitrary code on the victim's system with the privileges of the user running Acrobat or Reader. Anyone running an affected version of Adobe Acrobat or Reader is exposed, and because these PDF clients are near-ubiquitous on desktops, the potential affected population is very large. CISA added the flaw to its Known Exploited Vulnerabilities catalog on 2026-05-20, confirming active exploitation in the wild; EPSS assigns an 86.6% probability of exploitation within 30 days, while no public proof-of-concept is known and ransomware use has not been confirmed. Do: Inventory systems running Adobe Acrobat or Reader and upgrade to a patched version per Adobe's security advisory immediately, since the KEV listing invokes BOD 22-01 timelines for federal agencies. Until patched, filter or sandbox untrusted PDFs at email gateways and consider disabling PDF JavaScript in Reader where supported, a standard Adobe mitigation for this class of flaw. Verify installed versions against the vendor's affected-version list and monitor CISA and vendor advisories for updated indicators, noting ransomware use remains unconfirmed. | — | 87% | KEV |
| mass≈1M+ legacy/unpatched installs worldwide (Acrobat/Reader installed base is in the hundreds of millions) | |
| CVE-2010-0249 | Use-After-Free Remote Code Execution in Microsoft Internet Explorer Microsoft Internet Explorer contains a use-after-free flaw (CWE-416) in which the browser accesses a pointer to an object that has already been deleted, a defect historically associated with the January 2010 'Aurora' targeted attacks. The flaw is triggered when a user simply visits an attacker-crafted or attacker-controlled web page that forces the browser to free an in-use object and then dereference the dangling pointer during page rendering. Successful exploitation gives a remote attacker the ability to execute arbitrary code in the security context of the logged-on user, potentially installing programs; viewing, changing, or deleting data; or creating new accounts. Anyone running Internet Explorer is affected, especially organizations still relying on the now end-of-life/end-of-service browser on legacy Windows systems, which CISA says should discontinue use if mitigations are not applied. Exploitation is confirmed: CISA added the flaw to the Known Exploited Vulnerabilities catalog on 2026-05-20 and EPSS assigns a 91.9% probability of exploitation within 30 days (100th percentile), although no public proof-of-concept is cataloged. Do: Per CISA's KEV required action, apply Microsoft's mitigations: the January 2010 out-of-band cumulative security update for Internet Explorer (MS10-002) remediates this flaw, with workarounds including disabling Active Scripting or setting the Internet and Local intranet security zones to High. Inventory any systems still invoking Internet Explorer (legacy Windows builds and intranet apps) and migrate them to Microsoft Edge or another supported browser, discontinuing IE use entirely where mitigations are unavailable. | — | 92% | KEV |
| masshundreds of millions of legacy Windows/IE installs (IE held roughly 60% of global browser share when the flaw was disclosed) | |
| CVE-2010-0806 | Use-After-Free RCE in Microsoft Internet Explorer (CVE-2010-0806) Microsoft Internet Explorer contains a use-after-free (resource management) flaw in which the browser accesses an invalid pointer after an object has been deleted, leaving a dangling pointer. A remote attacker can trigger the flaw by luring a user of a vulnerable Internet Explorer version to attacker-controlled or malicious web content; the dangling-pointer access can be leveraged to execute arbitrary code with the victim user's privileges. Any system still running the affected Internet Explorer builds is exposed; the flaw dates to the 2010 era, when vendor advisories (cumulative update MS10-018, March 2010) addressed it in Internet Explorer 6 and 7, and CISA notes the impacted product may be end-of-life. Exploitation is confirmed in the wild: the flaw was added to the CISA Known Exploited Vulnerabilities catalog on 2026-05-20 (ransomware use unknown), and EPSS assigns an 82.2% probability of exploitation within 30 days; no public proof-of-concept is cataloged. Do: Apply mitigations per Microsoft's vendor instructions within the BOD 22-01 timeframe, which for affected builds means the MS10-018 (March 2010) cumulative Internet Explorer update; because IE 6/7 (and IE generally) are end-of-life/retired, CISA also permits discontinuing use of the product. Inventory the estate for Internet Explorer 6/7 on legacy Windows XP and embedded or unmanaged systems, and migrate any remaining users to a supported, currently patched browser rather than relying on the retired IE client. | — | 82% | KEV |
| large~100,000 to 1,000,000 residual legacy installations still running vulnerable IE 6/7 builds (out of the hundreds of millions of IE users when the flaw was… | |
| CVE-2025-34291 | CORS Origin Validation Flaw in Langflow Enables Account Takeover and RCE Langflow versions up to and including 1.6.9 chain two web-security weaknesses - a permissive CORS configuration (allow_origins='*' with allow_credentials=True) and a refresh-token cookie set with SameSite=None - into account takeover and remote code execution. When an authenticated Langflow user visits an attacker-controlled webpage, the browser silently sends credentialed cross-origin requests that successfully call the refresh endpoint, letting the attacker mint fresh access_token/refresh_token pairs for the victim's session (CWE-346). With those tokens, the attacker can access authenticated endpoints, including Langflow's built-in code-execution functionality, and run arbitrary code for full system compromise. Any Langflow deployment at or below version 1.6.9 is affected, with internet-facing instances most exposed. The flaw is being actively exploited: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-05-21, and EPSS assigns an 83.6% probability of exploitation within 30 days (100th percentile). Do: Upgrade Langflow to a release newer than 1.6.9 following vendor guidance, and invalidate existing sessions afterward. If patching must wait, correct the CORS configuration (do not combine allow_origins='*' with allow_credentials=True), stop marking the refresh-token cookie SameSite=None, and restrict internet exposure of the instance. Review access logs for refresh-endpoint calls from unexpected origins, rotate tokens and credentials for suspected victims, and follow BOD 22-01 requirements if you are a U.S. federal agency. | 9.4 | 84% | KEV PoC |
| largetens of thousands of self-hosted and internet-exposed instances plausibly affected (estimate) | |
| CVE-2026-0257 | Authentication Bypass in Palo Alto Networks PAN-OS GlobalProtect Portal and Gateway CVE-2026-0257 is an authentication bypass in the GlobalProtect portal and gateway of Palo Alto Networks PAN-OS that allows a remote, unauthenticated attacker to defeat security restrictions and establish an unauthorized VPN connection; incident reporting indicates it involves forged VPN cookies (CWE-565). An attacker who succeeds gains the network access of a legitimate remote-access user, and Qilin ransomware affiliates have been using this flaw as their initial access vector. Any organization running PAN-OS with the GlobalProtect portal or gateway enabled is in scope, including Siemens RUGGEDCOM APE1808 appliances that run PAN-OS, while Panorama and Cloud NGFW are explicitly not affected. Exploitation is confirmed in the wild: the flaw was added to CISA KEV on 2026-05-29 with ransomware use known, EPSS assigns it a 93.9% probability of exploitation within 30 days (100th percentile), and Rapid7 has documented attacks against multiple customers. Do: Upgrade PAN-OS to the fixed release specified in the Palo Alto Networks security advisory, and check Siemens' guidance if you operate RUGGEDCOM APE1808 appliances. Review GlobalProtect portal/gateway logs for forged VPN cookies and unauthorized VPN sessions, and hunt for Qilin ransomware indicators on hosts reachable through the VPN. If patching cannot happen immediately, restrict internet exposure of the GlobalProtect portal and gateway; federal agencies must apply mitigations per BOD 22-01 given the KEV listing. | 7.8 | 95% | KEV ransomware |
| massOn the order of hundreds of thousands of internet-exposed GlobalProtect portals/devices (mid-six figures) | |
| CVE-2026-0300 | Unauthenticated Out-of-bounds Write RCE in Palo Alto Networks PAN-OS Palo Alto Networks PAN-OS contains an out-of-bounds write vulnerability (CWE-787) in the User-ID Authentication Portal, also known as the Captive Portal service. An unauthenticated attacker can trigger the flaw by sending specially crafted packets to the portal, without needing valid credentials. Successful exploitation allows the attacker to execute arbitrary code with root privileges on the firewall, giving full control of PA-Series and VM-Series devices. Any organization running PA-Series or VM-Series firewalls with the User-ID Authentication Portal service enabled is affected. The flaw was added to CISA's Known Exploited Vulnerabilities catalog on 2026-05-06, indicating exploitation in the wild; EPSS puts the 30-day exploitation probability at 31.7% (98th percentile), patches were released on 2026-05-13, no public PoC is known, and CVSS scoring is not yet available. Do: Apply the PAN-OS patches Palo Alto Networks released on 5/13/2026, prioritizing internet-facing PA-Series and VM-Series firewalls. As an interim mitigation, restrict User-ID Authentication Portal access to trusted zones only, or disable the service entirely if it is not required. Inventory your deployments for use of the Captive Portal/User-ID Authentication Portal and follow CISA KEV and BOD 22-01 requirements, including for affected cloud service instances; note that federal agencies face KEV remediation deadlines. | 9.3 | 32% | KEV |
| large≈100,000+ PAN-OS firewall deployments; the vulnerable subset (installs with the User-ID Authentication Portal enabled) is likely in the tens of thousands,… | |
| CVE-2026-20182 | Authentication Bypass in Cisco Catalyst SD-WAN Control Components CVE-2026-20182 is a critical authentication flaw (CWE-287) in the control-connection peering authentication of Cisco Catalyst SD-WAN Controller (formerly vSmart), Manager (formerly vManage), and Validator (formerly vBond). Because the peering authentication mechanism does not work properly, an unauthenticated, remote attacker can send crafted requests during the control-connection handshake and log in to the controller as an internal, high-privileged, non-root user without valid credentials. With this access, the attacker can reach NETCONF and manipulate network configuration across the entire SD-WAN fabric. Any organization running these Catalyst SD-WAN control components is affected, and the flaw carries a CVSS 3.1 score of 10.0 and a 91.5% EPSS score. CISA added it to the Known Exploited Vulnerabilities catalog on 2026-05-14, confirming exploitation in the wild, amid a series of exploited Cisco SD-WAN zero-days including a compromise at a communications service provider. Do: Upgrade affected Catalyst SD-WAN Controller, Manager, and Validator components to the fixed releases identified in Cisco's May 2026 advisory (version numbers are not provided in this data). Use the advisory's 'show control connections' guidance to inspect control-connection handshaking for anomalies and audit for unauthorized high-privileged non-root accounts and unexpected NETCONF sessions. Operators — especially federal agencies — should follow CISA Emergency Directive 26-03 and CISA's Hunt & Hardening Guidance for Cisco SD-WAN Devices, including restricting internet exposure of SD-WAN management interfaces until patched. | 10.0 | 92% | KEV |
| largeon the order of tens of thousands of affected control-plane systems (controllers, managers, validators) across enterprise, service-provider, and government… | |
| CVE-2026-26980 | Unauthenticated SQL Injection in Ghost CMS Allows Arbitrary Database Reads Ghost CMS versions 3.24.0 through 6.19.0 contain an unauthenticated SQL injection flaw (CWE-89) that lets a remote attacker trigger arbitrary reads against the site's database over the network, with no privileges or user interaction required. The attacker gains read access to database contents — high confidentiality impact per the CVSS vector (C:H/I:N/A:N), which can expose user, post, and session data. Any Ghost deployment running a release within the affected range is exposed, and the fix is in version 6.19.1. The flaw is not yet in the CISA KEV catalog and no public PoC is catalogued, but news reports indicate active in-the-wild exploitation: attackers have already hijacked more than 700 Ghost sites and used them to deliver ClickFix social-engineering attacks. Do: Upgrade to Ghost 6.19.1 or later immediately if running any version from 3.24.0 through 6.19.0. Given the high EPSS (70.2% in 30 days) and confirmed mass exploitation, review logs for unauthenticated database-reading requests, rotate credentials and invalidate sessions in case sensitive data was read, and check site content and admin accounts for tampering consistent with the reported ClickFix hijacking campaign. | 7.5 | 70% |
| masshundreds of thousands of internet-facing Ghost sites; 700+ already confirmed hijacked | ||
| CVE-2026-31431 | Local Privilege Escalation (Copy Fail) in Linux Kernel algif_aead Interface CVE-2026-31431 ('Copy Fail') is an incorrect resource transfer between spheres (CWE-669/CWE-1288) in the Linux kernel's algif_aead implementation of the AF_ALG userspace crypto interface, introduced roughly nine years ago (around 2017, per public reporting) when commit 72548b093ee3 switched AEAD operations to in-place handling even though the source and destination buffers come from different mappings. A local, unprivileged user can trigger the flaw by performing AEAD operations through the AF_ALG socket interface, causing the kernel to mishandle the copy of ciphertext and associated data. Successful exploitation provides a reliable local privilege escalation to root (C:H/I:H/A:H per the CVSS vector). Nearly every major Linux distribution and enterprise platform is exposed, including the kernel itself, Red Hat Enterprise Linux (including AUS, EUS, TUS and Update Services for SAP Solutions), OpenShift Container Platform, Amazon Linux, Ubuntu, Debian, openSUSE Leap, SUSE CaaS Platform, NixOS, and Linux-based products from Arista and Siemens. The flaw has public proof-of-concept code, a 99.9% EPSS score, and was added to CISA's Known Exploited Vulnerabilities catalog on 2026-05-01, indicating exploitation in the wild (ransomware use is unknown). Do: Patch by installing the kernel update for CVE-2026-31431 through your distribution's security channel (Red Hat Enterprise Linux including AUS/EUS/TUS/SAP channels, OpenShift, Amazon Linux, Ubuntu, Debian, openSUSE Leap, SUSE CaaS Platform, NixOS, and Arista/Siemens firmware/software as applicable) and reboot into the patched kernel; the data provides no fixed version numbers, so defer to vendor advisories. Because the flaw is in CISA's KEV catalog (added 2026-05-01) with a 99.9% EPSS score, prioritize internet-reachable and multi-user systems first and follow BOD 22-01 guidance for cloud services. Check running kernel versions ('uname -r') and distribution advisory status to confirm you are on a fixed build. | 7.8 | 100% | KEV PoC ×5 |
| masshundreds of millions to billions of installations (servers, cloud instances, desktops, and Android/embedded devices running affected kernel generations) | |
| CVE-2026-34926 | Directory Traversal in Trend Micro Apex One (On-Premise) Server CVE-2026-34926 is a directory traversal vulnerability (CWE-23) in the on-premise edition of the Trend Micro Apex One endpoint management server. A pre-authenticated local attacker — someone with access to the Apex One server who has already obtained administrative credentials through some other method — can use the traversal to modify a key table on the server, injecting malicious code that the server then deploys to its managed agents. This gives the attacker a delivery channel to run malicious code on the agents managed by the exploited server (CVSS scope changed), which is why the 6.7 CVSS score reflects a local, high-complexity, high-privilege attack path with high confidentiality impact. Only on-premise Apex One deployments are exploitable; the cloud/SaaS edition is not affected by this flaw. The flaw is being actively exploited: CISA added it to the Known Exploited Vulnerabilities catalog on 2026-05-21 (EPSS 12.7%, 96th percentile), though no public proof-of-concept is known and ransomware use has not been confirmed. Do: Apply Trend Micro's fix for the Apex One on-premise server per the vendor security advisory (exact fixed versions are not stated in the available data — check the bulletin), or, for US federal agencies, satisfy the BOD 22-01/KEV required action of applying vendor mitigations or discontinuing use if mitigations are unavailable. Because exploitation requires administrative credentials obtained by some other method, review privileged accounts on Apex One servers for compromise, check the server's key table for unauthorized modifications, and look for unexpected or anomalous code distributed to managed agents. Ransomware use is unconfirmed but plausible; restrict local and administrative access to the server and monitor agent activity until patched. | 6.7 | 13% | KEV |
| largetens of thousands of on-premise Apex One server deployments worldwide (managed agent population likely in the millions); not publicly quantified | |
| CVE-2026-45498 +1 in the same advisory: …41091 | Denial-of-Service Vulnerability in Microsoft Defender Antimalware Platform CVE-2026-45498 is a denial-of-service flaw (CWE-400, uncontrolled resource consumption) in the Microsoft Defender antimalware platform, rated 7.5 (High) with a network attack vector and no privileges or user interaction required. A remote, unauthenticated attacker can trigger excessive resource consumption that disrupts the Defender service, with high impact on availability but no confidentiality or integrity impact per the CVSS scoring. An attacker gains the ability to crash, hang, or disable antimalware protection on targeted systems, potentially leaving endpoints temporarily unprotected. Any deployment of Microsoft Defender — which is the default antimalware on modern Windows and is also deployed as a cloud service — is in scope, and CISA's required action explicitly points defenders to BOD 22-01 guidance for cloud services. The flaw has been added to CISA's KEV catalog (2026-05-20), EPSS assigns it a 63.1% probability of exploitation within 30 days, and headlines confirm it is being exploited in the wild alongside CVE-2026-41091. Do: Apply mitigations per Microsoft's vendor instructions and follow applicable CISA BOD 22-01 guidance for cloud services, as required by the KEV entry. Ensure the Defender antimalware platform and its security intelligence updates are fully current on all endpoints, and check event logs for Defender service crashes or disabled protection that may indicate exploitation. Ransomware use is currently listed as unknown, so treat any Defender outage on exposed systems as a potential precursor to follow-on activity. | 7.5 group max | 63% | KEV |
| masshundreds of millions of Windows endpoints (Defender is the default antimalware on modern Windows client and server) | |
| CVE-2026-42208 | SQL Injection in BerriAI LiteLLM Proxy Exploited in the Wild BerriAI LiteLLM, an open-source proxy server (AI gateway) used to call LLM APIs in OpenAI or native format, contains a SQL injection (CWE-89) in the database query performed during proxy API key checks in versions 1.81.16 through before 1.83.7: the caller-supplied key value was mixed into the query text rather than passed as a parameter. An unauthenticated attacker triggers the flaw by sending a specially crafted Authorization header to any LLM API route (for example POST /chat/completions), reaching the vulnerable query through the proxy's error-handling path. Successful exploitation lets the attacker read data from the proxy's database and potentially modify it, leading to unauthorized access to the proxy and the API keys/credentials it manages; CVSS 4.0 rates it 9.3 (critical). Any organization running an affected LiteLLM proxy version is affected, particularly instances reachable over a network. Exploitation is confirmed in the wild: the flaw was reportedly exploited within 36 hours of disclosure, CISA added it to the Known Exploited Vulnerabilities catalog on 2026-05-08, and EPSS puts the 30-day exploitation probability at 89.4%. Do: Upgrade LiteLLM to version 1.83.7 or later immediately; exploitation began within 36 hours of disclosure, the flaw is in CISA's KEV catalog, and federal agencies must apply mitigations under BOD 22-01. Until patched, restrict network access to the proxy, and review proxy database logs for unexpected queries or unauthorized key usage; if compromise is suspected, rotate the API keys and credentials stored in the proxy database. Also check your exposure to the separately reported LiteLLM issue CVE-2026-42271, which is reported as exploited in the wild and chains to unauthenticated RCE. | 9.3 | 89% | KEV |
| largeroughly tens of thousands of self-hosted LiteLLM proxy deployments (exact counts unknown) | |
| CVE-2026-42897 | Cross-Site Scripting in Microsoft Exchange Server Actively Exploited by Laundry Bear CVE-2026-42897 is an improper-neutralization flaw (CWE-79) in Microsoft Exchange Server that lets an unauthenticated remote attacker perform cross-site scripting and carry out spoofing. Per the CVSS vector (AV:N/PR:N/UI:R), exploitation requires a victim to interact with attacker-controlled content — reported attacks by the Russian actor Laundry Bear (TA488) trigger when a crafted email is opened in Exchange's webmail interface (Outlook Web Access). The attacker gains the ability to spoof the victim within their webmail session, and reported intrusions show mailbox access persisting even after organizations rotate credentials. Any organization running on-premises Microsoft Exchange Server or Exchange Server Subscription Edition is potentially exposed, particularly those publishing webmail to the internet; specific affected version ranges are not provided in the available data. Exploitation is confirmed in the wild: the flaw was added to CISA KEV on 2026-05-15 and carries a very high EPSS score of 71.2%, though no public proof-of-concept is known. Do: Apply Microsoft's security update for CVE-2024-42897 to all on-premises Exchange and Exchange Subscription Edition servers per vendor guidance — no specific patch versions are provided in the available data, so consult the vendor advisory for build numbers. Federal agencies must patch or apply mitigations per BOD 22-01 given the KEV listing. Because reported attacks (Laundry Bear/TA488) maintain mailbox access after password resets, treat any suspected compromise as persistent: review OWA access logs and inbox rules for anomalies, and invalidate active webmail sessions and tokens, not just credentials. | 6.1 | 71% | KEV |
| large≈20,000+ internet-exposed Exchange servers (public-scan reporting) | |
| CVE-2026-45321 | Supply chain compromise: credential-stealing code in 42 @tanstack/* npm packages CVE-2026-45321 is a supply chain compromise in which 84 malicious versions across 42 @tanstack/* npm packages (including @tanstack/react-router, @tanstack/react-start, @tanstack/history, and related router/start packages) were published to the npm registry on 2026-05-11 between roughly 19:20 and 19:26 UTC, authenticated through TanStack's legitimate GitHub Actions OIDC trusted-publisher binding. The attacker chained three known weakness classes — a pull_request_target 'Pwn Request' misconfiguration, GitHub Actions cache poisoning across the fork-to-base trust boundary, and runtime memory extraction of the OIDC token from the Actions runner process — allowing publication under a trusted identity without modifying the publish workflow. Each affected package received exactly two malicious versions carrying credential-stealing malware, so developers, CI pipelines, or downstream builds that installed them could have npm, GitHub, and cloud credentials extracted; related reporting (FBI, StepSecurity) links the campaign to stolen cloud credentials and a self-spreading 'Mini Shai-Hulud' worm that also hit packages in other ecosystems such as Mistral AI and Guardrails AI. Exposure is limited to consumers who installed the two malicious versions published per package during the exposure window; other users of these widely deployed libraries were not affected by the malicious publishes. Exploitation is confirmed in the wild: the issue was added to CISA's Known Exploited Vulnerabilities catalog on 2026-05-27 with known ransomware use, and EPSS estimates a 2.3% probability of exploitation in the next 30 days (83rd percentile). Do: Audit lockfiles and CI logs for the affected @tanstack/* packages' versions published during the 2026-05-11 ~19:20-19:26 UTC window; if found, reinstall from clean versions per the TanStack postmortem (tanstack.com/blog/npm-supply-chain-compromise-postmortem) and rotate exposed credentials (npm tokens, GitHub PATs/secrets, cloud keys), treating any cached CI artifacts as suspect. Apply mitigations per vendor instructions and CISA BOD 22-01 guidance for cloud services, or discontinue use if mitigations are unavailable, and remediate the underlying CI weaknesses (pull_request_target handling, Actions cache hygiene, and OIDC token handling) to prevent recurrence. | 9.6 | 2% | KEV ransomware PoC ×2 |
| large~100,000+ downstream installs/CI runs (estimate) | |
| CVE-2026-48027 | Malicious Code Embedded in Nx Console VS Code Extension 18.95.0 CVE-2026-48027 is a supply-chain compromise in which version 18.95.0 of Nx Console, the Visual Studio Code UI for the Nx and Lerna build tools, was published with embedded malicious code (CWE-506). The compromised release was live on the Visual Studio Marketplace for roughly 18 minutes (12:30-12:48 UTC) and on OpenVSX for about 36 minutes (12:33-13:09 UTC) on 19 May 2026, so developers whose clients pulled the update during those windows had the malicious extension installed. An attacker gains code execution on developer workstations and used it to steal cloud and CI credentials; the compromise has been tied to a breach of GitHub internal repositories and is associated with ransomware activity. Only users who installed Nx Console 18.95.0 are affected, and version 18.100.0 is not compromised. CISA added the flaw to the Known Exploited Vulnerabilities catalog on 27 May 2026 with known ransomware use, and public analysis is available from StepSecurity. Do: Upgrade to Nx Console 18.100.0 immediately; if 18.95.0 was installed on 19 May 2026, treat local secrets as compromised and rotate GitHub tokens, cloud and CI credentials, npm tokens, and SSH keys on affected machines, and review repositories and pipelines for tampering. Follow CISA KEV/BOD 22-01 required actions and review the StepSecurity blog post for indicators of compromise. | 9.3 | 2% | KEV ransomware PoC |
| moderatelikely tens of thousands of developer workstations (the subset of Nx Console's roughly one-million-install developer base whose clients auto-updated to 18.95.0… | |
| CVE-2026-48172 | Privilege Escalation (Possible Root) in LiteSpeed cPanel Plugin CVE-2026-48172 is a critical privilege-escalation flaw (CWE-266, incorrect privilege assignment) in the LiteSpeed User-End cPanel plugin before 2.4.5, stemming from mishandling of the plugin's Redis enable/disable feature. It is exploitable over the network without authentication or user interaction (CVSS 4.0: AV:N/AC:L/PR:N/UI:N), and exploitation leaves traces of requests to the cPanel API's redisAble function in cPanel logs. An attacker who exploits it can elevate privileges to possibly root on the hosting server, meaning a single attacker could take control of every account and site hosted on that server. At risk are hosting providers and organizations running cPanel/WHM with the LiteSpeed cPanel plugin (and the related WHM plugin), a common premium web-server setup on multi-tenant shared-hosting platforms. The flaw was exploited in the wild in May 2026, was added to CISA's KEV catalog on 2026-05-26, and carries an EPSS of 18.9% (97th percentile); no public PoC is known. Do: Upgrade the LiteSpeed User-End cPanel plugin to at least version 2.4.7 (versions before 2.4.5 are affected; 2.4.7 is the recommended minimum). Hunt for exploitation by running grep -rE "cpanel_jsonapi_func=redisAble" /var/cpanel/logs /usr/local/cpanel/logs/ 2>/dev/null in Bash: no output means you were not hit, while hits should be validated (confirm the listed IPs are legitimate, block any that are not, and review system logs for actions taken by those IPs). Because this is a CISA KEV entry (added 2026-05-26), apply the vendor fix per BOD 22-01 timelines or discontinue use of the product if mitigations are unavailable. | 10.0 | 19% | KEV |
| largelikely tens of thousands of multi-tenant cPanel hosting servers (order of 10k-50k), with 100k+ tenant accounts behind them | |
| CVE-2026-6973 | Authenticated RCE in Ivanti Endpoint Manager Mobile (EPMM) Ivanti Endpoint Manager Mobile (EPMM) contains an improper input validation flaw (CWE-20) that allows a remotely authenticated user with administrative access to achieve remote code execution on the server. An attacker triggers it by sending crafted input to the EPMM management interface after authenticating with administrative credentials, so compromise or misuse of an admin account is the likely path to exploitation. Successful exploitation yields code execution on the EPMM server, giving an attacker a foothold in the organization's mobile device management infrastructure and potential access to data managed through it. Any organization running Ivanti EPMM, typically enterprises using it as their MDM platform, is affected; the available data does not specify affected version ranges. The vulnerability was added to CISA's Known Exploited Vulnerabilities catalog on 2026-05-07, confirming active exploitation (ransomware use unknown), and it carries a high 34.5% EPSS for exploitation in the next 30 days. Do: Update EPMM to the patched release identified in Ivanti's advisory, as required under CISA KEV and BOD 22-01 for federal agencies. Until patched, restrict and audit administrative access to EPMM, review authentication and admin-activity logs for signs of abuse, and limit exposure of the management interface to trusted networks. | 7.2 | 34% | KEV |
| largetens of thousands of EPMM deployments worldwide | |
| CVE-2026-8398 | Trojanized Installer Backdoor in DAEMON Tools Lite (Supply Chain Compromise) CVE-2026-8398 (CWE-506, embedded malicious code) is a supply chain compromise in which attackers gained access to AVB Disc Soft's build or distribution infrastructure and trojanized the official Windows installers of DAEMON Tools Lite versions 12.5.0.2421 through 12.5.0.2434, distributed from the legitimate site daemon-tools.cc between approximately April 8 and May 5, 2026. The flaw is triggered by installing or running one of these tampered builds, which shipped backdoored copies of DTHelper.exe, DiscSoftBusServiceLite.exe, and DTShellHlp.exe digitally signed with the vendor's legitimate code-signing certificate, allowing them to bypass signature-based detection. Once executed, the embedded backdoor gives attackers a trusted foothold and code execution on the affected Windows host, potentially enabling credential theft, further compromise, or ransomware follow-on activity (ransomware linkage currently unknown). Anyone who downloaded and installed DAEMON Tools Lite from the official site during the affected window is impacted; users with other or older builds are not part of this trojanized distribution. The issue was added to CISA's Known Exploited Vulnerabilities catalog on 2026-05-27, confirming exploitation in the wild, and a public technical write-up is available via Kaspersky's Securelist. Do: Identify hosts that installed DAEMON Tools Lite 12.5.0.2421–12.5.0.2434 from daemon-tools.cc during the affected window; remove/reinstall the software from a clean, current build obtained from the vendor and verify the signatures of DTHelper.exe, DiscSoftBusServiceLite.exe, and DTShellHlp.exe. Because the trojanized binaries were validly signed, treat affected systems as potentially compromised and hunt for persistence, anomalous process activity, and C2 traffic associated with the backdoor. Federal agencies must apply vendor mitigations per BOD 22-01 guidance or discontinue use of the product by the KEV deadline (listed 2026-05-27). | 9.3 | 1% | KEV PoC |
| largeplausibly ~100,000–1,000,000 Windows installs of the affected builds during the ~4-week trojanized distribution window | |
| CVE-2026-9082 | Actively Exploited SQL Injection in Drupal Core CVE-2026-9082 is a critical SQL injection flaw (CWE-89) in Drupal core caused by improper neutralization of special elements used in SQL commands, allowing user-controlled input to alter the queries the application executes. The CVSS vector (AV:N/AC:L/PR:N/UI:N) shows it is remotely exploitable over the network without authentication, special privileges, or user interaction. A successful attacker gains high-impact access to the database (read, modify, or disrupt data), and news reports indicate PostgreSQL-backed sites may additionally be exposed to remote code execution. It affects Drupal core from version 8.9.0 onward across all current major lines, with fixes in 10.4.10, 10.5.10, 10.6.9, 11.1.10, 11.2.12, and 11.3.10, meaning essentially all unpatched modern Drupal deployments are at risk. The flaw is confirmed under active attack: CISA added it to the KEV catalog on 2026-05-22 and headlines report it is already being exploited in the wild, while EPSS assigns an 87.9% 30-day exploitation probability (100th percentile); no public proof-of-concept is known yet. Do: Upgrade Drupal core immediately to the patched release for your branch: 10.4.10, 10.5.10, 10.6.9, 11.1.10, 11.2.12, or 11.3.10, or a later release as applicable, since the flaw is being actively exploited and carries an 87.9% EPSS. Prioritize internet-facing sites and deployments using a PostgreSQL database, which reports say can be pushed to remote code execution, and review web and database logs for signs of exploitation. Under the CISA KEV listing (added 2026-05-22), U.S. federal agencies must apply vendor mitigations per applicable BOD 22-01 guidance or discontinue use of the product if mitigations are unavailable. | 9.8 | 88% | KEV |
| masslikely hundreds of thousands to 1M+ sites worldwide (all modern Drupal core branches affected) |
Indicators of compromiseauto-extracted · verify before use · export allAll →
| Type | Indicator | Context |
|---|---|---|
| domain | web-telegram.ug | m logs in Enumerates running processes Sends DNS request to web-telegram[.]ug Further technical details associated with this activity, |
| sha256 | 7790fd1035266000ed6d6cc35822f7683f5271663af8a5b5effadff85316df6d | indows registry Drops files named UtilifySetup.tmp (SHA256: 7790fd1035266000ed6d6cc35822f7683f5271663af8a5b5effadff85316df6d) and Grape.exe Enumerates files and directories Retrieves s |
Full article2,393 words · extracted from recordedfuture.com · click to collapse
In May 2026, Insikt Group® identified 41 high-impact vulnerabilities that should be prioritized for remediation, all of which had a Very Critical Recorded Future Risk Score. This represents an 11% increase from last month.
These vulnerabilities affected products from 20 vendors. 21 of the 41 vulnerabilities were included in the US Cybersecurity and Infrastructure Security Agency (CISA)’s Known Exploited Vulnerabilities (KEV) catalog, 19 were surfaced through honeypot data, and one was reported by a cybersecurity vendor.
The 41 vulnerabilities in this report affected products from 20 vendors. Vercel accounted for approximately 27% of the vulnerabilities, driven by honeypot-sourced Next.js activity. The remaining exposure was concentrated across a range of enterprise software, security, networking, developer tooling, and cloud-related products.
Quick Reference: May 2026 Vulnerability Table
All 22 vulnerabilities below were actively exploited in May 2026. This table does not include the 19 CVEs associated with honeypot activity, which are available to Recorded Future customers via the CVE Monthly Report. The table below also provides examples of public PoCs identified by Insikt Group®. These PoCs were not tested for accuracy or efficacy. Vulnerability management teams should exercise caution and verify the validity of PoCs before testing.
#
Vulnerability
Risk
Score
Vendor/Product
KEV
Malware Analysis
RCE
PoC
1
CVE-2008-4250
99
Microsoft Windows
✓
✓
2
CVE-2009-1537
99
Microsoft DirectX
✓
3
CVE-2009-3459
99
Adobe Acrobat and Reader
✓
4
CVE-2010-0249
99
Microsoft Internet Explorer
✓
5
CVE-2010-0806
99
Microsoft Internet Explorer
✓
✓
(available to Recorded Future Customers)
6
CVE-2025-34291
99
Langflow
✓
7
CVE-2026-0257
99
Palo Alto Networks PAN-OS, Cloud NGFW, and Prisma Access
✓
8
CVE-2026-0300
99
Palo Alto Networks PAN-OS, Cloud NGFW, Prisma Access
✓
9
CVE-2026-20182
99
Cisco Catalyst SD-WAN and SD-WAN Manager
✓
10
CVE-2026-31431
99
Linux Kernel
✓
✓
(available to Recorded Future Customers)
11
CVE-2026-34926
99
Trend Micro Apex One (On-Premise)
✓
12
CVE-2026-41091
99
Microsoft Defender
✓
13
CVE-2026-42208
99
BerriAI LiteLLM
✓
14
CVE-2026-42897
99
Microsoft Exchange Server
✓
15
CVE-2026-45321
99
TanStack (Multiple Packages)
✓
16
CVE-2026-45498
99
Microsoft Defender
✓
17
CVE-2026-48027
99
Nx Console
✓
18
CVE-2026-48172
99
LiteSpeed cPanel Plugin
✓
19
CVE-2026-6973
99
Ivanti Endpoint Manager Mobile (EPMM)
✓
✓
20
CVE-2026-8398
99
Daemon Tools Lite
✓
21
CVE-2026-9082
99
Drupal Core
✓
22
CVE-2026-26980
99
Ghost CMS
✓
(available to Recorded Future Customers)
Table 1: List of vulnerabilities that were actively exploited in May, 2026 based on Recorded Future data (excluding honeypot-sourced CVEs).
Key Trends: May 2026
- In May 2026, threat actors exploited a Ghost CMS vulnerability in large-scale ClickFix and FakeCaptcha poisoning campaigns.
- The campaigns used compromised Ghost CMS websites to inject malicious JavaScript, redirect victims through social engineering lures, and stage dropper and loader payloads from attacker-controlled infrastructure.
- 12 of the 41 vulnerabilities enabled remote code execution (RCE), affecting products from 8 vendors: Microsoft, Adobe, Langflow, Palo Alto Networks, Apache, openDCIM, Fortinet, and Ivanti.
- Insikt Group identified public proof-of-concept (PoC) exploits for 32 of the 41 vulnerabilities reported this month.
- The most commonly observed flaws this month were CWE-79 (Cross-site Scripting), CWE-506 (Embedded Malicious Code), and CWE-89 (SQL Injection), with three CVEs each.
- 5 of the 41 vulnerabilities in this month’s prominent vulnerabilities table were first disclosed between 2008 and 2010, making them at least 15 years old, with the oldest vulnerability being approximately 18 years old.
- This reinforces our finding that attackers continue to exploit long-known weaknesses in environments where patching has lagged.
- Additionally, the fastest observed time from a vulnerability’s public disclosure to exploitation was less than one day.
Exploitation Analysis
This section highlights some of the highest-impact, actively exploited vulnerabilities this month, specifically those linked to known threat actor campaigns or that have public PoC exploits available. Vulnerabilities with no meaningful public technical detail are summarized in the quick reference table above only.
Threat Actors Exploit CVE-2026-26980 in Ghost CMS To Conduct Large-Scale ClickFix Poisoning Campaigns, Sample Available From Recorded Future Malware Intelligence
On May 21, 2026, cybersecurity firm XLab published a technical analysis detailing large-scale ClickFix poisoning campaigns targeting vulnerable Ghost Content Management System (CMS) instances by exploiting CVE-2026-26980. Ghost CMS allows users to create, manage, and publish content for blogs, media sites, newsletters, and subscription-based websites through a node.js-based publishing platform.
CVE-2026-26980 is a critical SQL injection vulnerability in Ghost CMS that allows unauthenticated threat actors to extract Ghost Admin API Keys and modify website content through the Ghost Admin API.
As previously reported by Insikt Group®, at least two threat groups exploited CVE-2026-26980 to inject malicious JavaScript into more than 700 compromised Ghost CMS websites across industries, including blockchain, artificial intelligence (AI), and financial technology (fintech). According to XLab, the threat actors used the compromised websites to deliver ClickFix and FakeCaptcha social engineering attacks that tricked victims into executing malicious commands and malware payloads on their systems.
Insikt Group® obtained one of the malicious samples, UtilifySetup.exe, from Recorded Future Malware Intelligence. The sample matched the sandbox YARA rule for detecting Inno Setup packaging. Based on sandbox and static code analysis, the sample performs the following actions on a victim’s machine:
- Conducts DLL injection
- Retrieves the system language and geolocation using the Windows registry
- Drops files named
UtilifySetup.tmp(SHA256: 7790fd1035266000ed6d6cc35822f7683f5271663af8a5b5effadff85316df6d) andGrape.exe - Enumerates files and directories
- Retrieves system information
- Delays execution using the Sleep API function for evasion
- Detects debuggers using the
GetTickCountAPI function to compare the timing and theIsDebuggerPresentAPI function - Creates a file inside the
C:\Users\user\AppData\Local\SuperMaxionQuickMaxlitedirectory, corroborating XLab’s analysis - Terminates running processes
Sandbox analysis categorized UtilifySetup.tmp as malicious due to the sample exhibiting discovery capabilities. Based on sandbox and static code analysis, the sample performs the following actions on a victim’s machine:
- Conducts DLL injection
- Retrieves the system language and geolocation using the Windows registry
- Executes
UtilifySetup.exeinstaller from the%Temp%directory using internal Inno Setup /SL5 launch parameters - Executes a file named
Grape.exeinside theC:\Users\user\AppData\Local\SuperMaxionQuickMaxlitedirectory
Once executed, Grape.exe performs the following actions on a victim’s machine:
- Adds a Windows registry Run key entry named
electron.app.Grapeset to execute itself when the victim logs in - Enumerates running processes
- Sends DNS request to
web-telegram[.]ug
Further technical details associated with this activity, including sample analysis, MITRE ATT&CK techniques, and IoCs, are available to Recorded Future customers via Insikt Group® reporting.
Recorded Future customers can also access Malware Intelligence queries that surface samples communicating with campaign-associated URLs, domains, and IP addresses.
Figure 1: Risk Rules History from Vulnerability Intelligence Card® for CVE-2026-26980 in Recorded Future (Source: Recorded Future)
Technical Blog and Alleged PoC for Actively Exploited Critical SQL Injection Vulnerability Affecting BerriAI LiteLLM (CVE-2026-42208)
On April 27, 2026, Michael Clark published a technical report on Sysdig detailing CVE-2026-42208. The Sysdig Threat Research Team observed the first exploitation attempt 36 hours and seven minutes after GitHub advisory GHSA-r75f-5x8p-qvmc, later assigned CVE-2026-42208.
On May 5, 2026, GitHub user Ashraf Zaryouh (0xBlackash on GitHub) shared an alleged PoC exploit for CVE-2026-42208. On May 8, 2026, CISA added CVE-2026-42208 to its KEV catalog. CVE-2026-42208 is a critical Structured Query Language (SQL) Injection vulnerability affecting BerriAI LiteLLM versions 1.81.16 to 1.83.6.
BerriAI LiteLLM is a proxy server and an AI gateway used to call large language model (LLM) application programming interfaces (APIs) in OpenAI-compatible or native formats, helping route requests and manage model access and credentials across providers.
Exploiting CVE-2026-42208 allows unauthenticated remote threat actors to read and potentially modify LiteLLM proxy database data, resulting in unauthorized access to the proxy and the credentials it manages. On April 21, 2026, LiteLLM released version 1.83.7 and later to fix CVE-2026-42208. If upgrading immediately is not possible, administrators can set disable_error_logs: true under general_settings to remove the code path through which unauthenticated input reaches the vulnerable query.
The vulnerability resides in the LiteLLM proxy application programming interface (API) key verification logic, where affected versions insert the caller-supplied Bearer token into an SQL query against the LiteLLM_VerificationToken table rather than passing the value through parameter binding. This unsafe query construction allows a threat actor to manipulate the database query before authentication completes.
The vulnerable code path runs during the pre-authentication API key validation process for reachable OpenAI-compatible API routes, including POST /chat/completions, and processes unauthenticated HTTP requests before identity-based access controls can apply. The affected verification path also exposes access to high-value LiteLLM data stores, including virtual API keys, provider credentials, and proxy configuration values. As a result, an unauthenticated remote threat actor with network access to the proxy could read data from the backend database and modify database records, exposing LiteLLM-managed API keys, provider credentials, and proxy configuration values. This exposure could lead to unauthorized access to the LiteLLM proxy and the credentials it manages.
According to the Sysdig report, the observed exploitation required network access to a LiteLLM proxy reachable by the threat actor and a request path that triggered proxy key verification, such as POST /chat/completions or /v1/chat/completions. The observed activity occurred in two phases: Sysdig attributed the first to the same operator using two adjacent egress IP addresses, followed by a short unauthenticated probe of key-management endpoints.
For Phase 1, the threat actor used 65[.]111[.]27[.]132 to conduct schema enumeration against a reachable LiteLLM proxy. The threat actor sent POST /chat/completions requests with the Python/3.12 aiohttp/3.9.1 user agent and an Authorization header beginning with Bearer sk-litellm, using the single quote to terminate the expected key string and inject UNION-based SQL queries. The threat actor targeted LiteLLM tables containing virtual API keys, stored provider credentials, and proxy environment configuration, including a retry from the lowercase litellm_verificationtoken table name to the quoted PascalCase LiteLLM_VerificationToken table name.
Sysdig assessed this retry as evidence of LiteLLM schema awareness rather than generic scanning. After a ten-minute pause, the same IP performed column-count enumeration by varying the number of NULL placeholders in UNION payloads to identify the expected query shape and return leaked data in the response body.
For Phase 2, the threat actor shifted to a second adjacent egress IP address, 65[.]111[.]25[.]67, after a 21-minute pause. The second IP belonged to the same /22 and AS200373 network context as the Phase 1 source and used the same Python/3.12 aiohttp/3.9.1 user agent. The threat actor replayed and refined the prior UNION-based SQL injection payloads, performed additional column-count discovery by varying NULL placeholders, and focused on LiteLLM tables associated with verification tokens, stored credentials, and proxy environment configuration. The threat actor also probed /key/generate and /key/info without authentication and ended with a terminal sk-litellm OR 1=1– payload, which Sysdig assessed as consistent with an automation harness exhausting its payload list. Sysdig reporting did not identify confirmed follow-through, such as authenticated key reuse, new virtual-key creation, or chained provider credential reuse.
Based on Ashraf Zaryouh’s repository, the PoC requires a target LiteLLM server URL and, optionally, a custom SQL payload and endpoint path. If the operator does not provide a custom payload, the PoC uses the default boolean-based payload 1' OR '1'='1. If the operator does not provide a custom endpoint path, the PoC targets /chat/completions.
Once the threat actor provides the target URL, the PoC removes trailing slashes, combines it with the selected endpoint path, prepends the payload with sk- to resemble a LiteLLM API key, and places the crafted value in the Authorization: Bearer header. It then prepares a normal-looking chat completion request body with a model name and a simple user message.
The PoC sends an HTTP POST request with the crafted authorization header and JSON body, unconditionally disables TLS certificate verification, suppresses the related warning, and uses a ten-second timeout. After receiving a response, it prints the HTTP status code, response length, and first 500 characters of the response for manual review. The PoC treats 200, 400, 401, and 500 responses as possible indicators that the request reached the relevant backend code path, but these status codes do not confirm successful SQL injection.
It also checks the response body for error or sql as indicators of a potential error path. If the request fails due to a timeout, connection issue, DNS failure, or similar error, the PoC catches the exception and prints the failure message instead of unexpectedly terminating. After the request completes or an exception occurs, the PoC prints a reminder message stating that the PoC serves demonstration purposes only and recommends upgrading LiteLLM to version 1.83.7 or later.
Insikt Group® has not tested this PoC for accuracy or efficacy. At the time of writing, the alleged PoC has been forked once on GitHub. Further technical details associated with this activity, including MITRE ATT&CK techniques and IoCs, are available to Recorded Future customers via Insikt Group® reporting.
Take Action
Timely and relevant information on vulnerabilities in your environment and that of your vendors and suppliers is critical for reducing risk. Find out how Recorded Future can support your team by increasing visibility, improving efficiency, and enabling confident decisions.
Vulnerability Intelligence – Prioritize vulnerabilities based on the likelihood of exploitation – not just the severity. Easily understand the risk of exploitation alongside severity, and real-time contextualized intelligence to help you quickly make confident decisions, patch what matters, and prevent attacks.
Attack Surface Intelligence – Identify internet-facing assets vulnerable to a specific CVE. Attack Surface Intelligence provides an outside-in view of your organization to help you actively discover, prioritize, and respond to unknown, vulnerable, or misconfigured assets.
Third-Party Intelligence – Gain an external view of the security posture of your vendors and partners. Eliminate time-consuming research and vendor communication cycles with the ability to promptly assess vulnerabilities in their internet-facing systems.
Insikt Group® – Receive access to exclusive reports on new vulnerabilities and trends from Recorded Future’s team of experts, the Insikt Group®. Download Nuclei templates created by Insikt Group® for select CVEs to test potentially vulnerable instances.
Recorded Future Professional Services – Work with our Professional Services team on a Vulnerability Analysis Engagement. Designed to equip your team with advanced strategies for identifying, prioritizing, and mitigating threats effectively, this program delves into technologies and operations essential for a successful vulnerability management program. (Learn more about how our Professional Services team can help your elevate your team by watching our recent Vulnerability Prioritization Workshop)
About Insikt Group®
Recorded Future’s Insikt Group®, the company’s threat research division, comprises analysts and security researchers with deep government, law enforcement, military, and intelligence agency experience. Their mission is to produce intelligence that reduces risk for customers, enables tangible outcomes, and prevents business disruption.
Text extracted automatically; images, tables and formatting may be missing. Original: https://www.recordedfuture.com/blog/may-2026-cve-landscape