Qilin ransomware ecosystem
Check Point assesses the IKEv1 VPN campaign connection with medium confidence; this does not attribute every exploit attempt.[14]Evidence dated Jul 2026
AI-generated, AI-updated weekly, AI quality-checked, and source-cited, this rolling 90-day product reviews the complete IntelliOS catalog and dozens of government, vendor, incident-response, exposure, insurance, and research sources to identify named technologies under active exploitation. It tells executives which owned products can create an incident now, why they matter to the business, what evidence to monitor, and which IntelliOS products contain the deeper campaign, actor, vulnerability, and response analysis.
| Field | Value | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Decision Question / User Topic | Named enterprise technologies under active exploitation during the rolling 90-day period and the business risk they create for owners. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Interpreted Questions | Which products are being exploited now according to CISA KEV? Which NVD/CNA severity, CVSS vector, and CWE weakness fields explain how the risk works? Which CWE patterns recur across the watchlist without being mistaken for proof of exploitation or a shared root cause? Who is likely to own each product, what can attackers reach after compromise, and when must remediation become incident response rather than a routine patch? | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Initial Observations | CISA added 70 KEVs across 37 vendors and 54 product families from April 30 through July 28; seven are marked for known ransomware use and 46 carried federal action windows of three days or less. The July 27 addition of FortiOS CVE-2025-68686 shows why KEV, CVSS, and CWE must be read together: CISA confirms exploitation, the CNA rates the isolated CVE 5.9 Medium because prior filesystem compromise makes attack complexity high, and Fortinet maps the confidentiality consequence to broad CWE-200. The highest-priority products sit near remote access, credentials, sensitive business data, developer secrets, or trusted automation. This card therefore ranks named products—not generic technology categories—and separates patching from the need to investigate prior exposure.[20]Evidence dated Current definition checked 2026-07-28 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Source Coverage |
Complete Tier 0–8 counts are shown here. The 2 retained sources and their claim treatment are identified in Citations. Planned integrations are not counted as checked or selected. |
Reporting-Period Statistics
At-a-glance measures from the retained evidence set. Citations identify the source controlling each statistic.
Period Coverage
90 calendar days, inclusive. Records are included by their first-observed date inside this window; the period does not imply that every underlying incident began or was confirmed during it.
Intended Reader and Decision Context
Who this brief is written for, the geographic and organizational lens it uses, and how readers should apply the intelligence.
| Audience Field | Assessment |
|---|---|
| Audience fieldPrimary audience | AssessmentBoards, CISOs, CIOs, risk and insurance leaders, vulnerability and asset owners, incident-response teams, MSPs, brokers, underwriters, and executives accountable for operational resilience. |
| Audience fieldOrganization profile | AssessmentU.S.-oriented with global source coverage; useful to SMB, midmarket, enterprise, government, education, manufacturing, technology, healthcare, professional services, hosting, and managed-service organizations. |
| Audience fieldDecision perspective | AssessmentUse the card to convert a broad vulnerability feed into named ownership questions: Do we operate it? Was it exposed? Is it fixed? Can we prove it remained trustworthy before the fix? Which credentials, workflows, data, or business services require containment or recovery? |
| Audience fieldNot a substitute for | AssessmentAn authenticated asset inventory, vendor-specific applicability review, forensic investigation, legal advice, policy interpretation, or a complete vulnerability-management program. |
Bottom Line Up Front
FortiOS CVE-2025-68686 is an incident-history question, not only a patch task: Fortinet says the bypass follows earlier filesystem-level compromise, while CISA requires BOD 26-04 forensic triage. Its 5.9 Medium score reflects that hard prerequisite; CWE-200 captures the confidentiality consequence but is too broad to stand in for the exploit's root cause. Owners must determine whether attacker-created persistence or altered trust survived before the fixed release was installed.[20]Evidence dated Current definition checked 2026-07-28
The card is an evidence-backed watchlist, not a compromise declaration: CISA, vendors, responders, insurers, and IntelliOS products answer different questions. The table preserves those boundaries while giving owners one coherent action queue.[14]Evidence dated Jul 2026
Decision Context
FortiOS CVE-2025-68686 reinforces that same point with unusually direct vendor and government language. Fortinet says exploitation bypasses a fix for symbolic-link persistence after another vulnerability already delivered filesystem-level compromise. The CNA's 5.9 Medium score reflects that high-complexity prerequisite and rates confidentiality impact High. Fortinet's CWE-200 mapping describes unauthorized information exposure, but MITRE cautions that CWE-200 is broad and discouraged as a precise root-cause mapping. CISA’s KEV action pairs vendor mitigation with BOD 26-04 forensic triage. FortiOS 7.6.0–7.6.1 should move to 7.6.2 or later and 7.4.0–7.4.6 to 7.4.7 or later; owners of the listed 7.2, 7.0, and 6.4 branches should obtain supported migration guidance rather than assume a fixed release exists in those branches.[20]Evidence dated Current definition checked 2026-07-28
Executive Briefing Priorities
FortiOS CVE-2025-68686 requires remediation plus historical investigation — The Fortinet advisory makes prior compromise a prerequisite. The 5.9 Medium score and CWE-200 classification explain complexity and confidentiality impact; they do not reduce the KEV response requirement. Preserve evidence, apply a documented fixed branch, hunt persistence and configuration change, rotate exposed trust material, and validate downstream access before closing the event.[20]Evidence dated Current definition checked 2026-07-28
Company Exposure and Exploitability
Specific products and control interfaces elevated by the retained government record. Each row explains the exploitable condition, which companies should care, the business consequence, and the evidence a defender should monitor.
| Technology and exploitable condition | Company exposure and business risk | Monitoring and IntelliOS coverage |
|---|---|---|
| Technology Fortinet FortiOS · CVE-2025-68686[20]Evidence dated Current definition checked 2026-07-28 Exploitable conditionFortinet says a remote unauthenticated attacker can bypass a fix for symbolic-link persistence after the device was already compromised at filesystem level through another vulnerability. CVSS is 5.9 Medium; CWE-200 captures the confidentiality consequence but is a broad classification. | Which companies should care Organizations and service providers operating affected FortiOS 7.6.0–7.6.1, 7.4.0–7.4.6, 7.2.0–7.2.13, 7.0.0–7.0.19, or 6.4.0–6.4.16 devices. Business riskAttacker persistence can survive an incomplete remediation, leaving perimeter trust, administrator credentials, configuration, sessions, routing, and connected networks at risk. | What to monitor Move 7.6 to 7.6.2+ and 7.4 to 7.4.7+; obtain supported migration guidance for listed older branches; preserve evidence; review filesystem and configuration integrity, accounts, sessions, credential use, outbound traffic, and downstream access. IntelliOS coverage |
| Technology Check Point Security Gateway IKEv1 remote access · CVE-2026-50751[14]Evidence dated Jul 2026 Exploitable conditionAuthentication bypass affects deprecated IKEv1 VPN configurations and is actively exploited. | Which companies should care Organizations retaining legacy Check Point remote-access configurations. Business riskUnauthorized perimeter access, credential or session abuse, internal reconnaissance, data theft, ransomware deployment, and emergency VPN disruption. | What to monitor IKEv1 configuration; hotfix status; unusual VPN authentications; new source geography; privileged access; lateral movement; Qilin-linked downstream behavior. IntelliOS coverage |
Source-Bound Actor Context
Check Point assesses the IKEv1 VPN campaign connection with medium confidence; this does not attribute every exploit attempt.[14]Evidence dated Jul 2026
Malware, Implants, and Intrusion Tooling
Source-backed malware and malicious tooling named in the retained campaigns. The table distinguishes malware families, open-source tools, custom implants, exploit or collection tooling, and reported outcomes that lack a publicly identified sample.
| Malware / tooling | Classification and campaign | Capability and potential impact | What defenders should monitor |
|---|---|---|---|
| Malware / toolingQilin ransomware[14]Evidence dated Jul 2026 | Classification and campaignRansomware and data-extortion ecosystemCheck Point assesses a medium-confidence association with exploitation of CVE-2026-50751. | Capability and potential impactCan turn edge access into data theft, encryption, operational interruption, ransom pressure, legal response, and recovery cost. | What defenders should monitorVPN-originated reconnaissance; credential access; privileged movement; exfiltration; backup/hypervisor access; encryption precursors. |
Current Carry-Forward Watchlist
Prioritized source-backed developments that convert the rolling activity record into named operational monitoring requirements.
| # | Threat / Category | Why It Matters | What to Monitor | IntelliOS Coverage |
|---|---|---|---|---|
| 1 | Threat / Category Network edge Fortinet FortiOS[20]Evidence dated Current definition checked 2026-07-28 | Why it mattersCVE-2025-68686 can bypass a prior fix for symbolic-link persistence after filesystem-level compromise. Track its KEV status, 5.9 Medium vector, and broad CWE-200 mapping as separate fields. | What to monitorAffected and historical versions, fixed-branch migration, filesystem and configuration integrity, accounts, sessions, credential access, outbound traffic, and downstream network activity. | IntelliOS coverage |
Automation Transparency
| Agent | Exploitable Technology Risk Rolling Intelligence Card Publisher |
|---|---|
| Status | Active · rolling 90-day automation |
| Cadence | Weekly on Friday at 1:00 PM ET |
| Previous run | No completed run is retained within the active rolling window · Run Not available |
| Previous result | The previous recorded run is outside the current 90-day coverage window and is not displayed. |
| What the previous run found |
|
| Next run | At midday ET on the card's configured weekly review day. |
| Sources monitored |
|
| Publication and alert policy | Publish and alert only when a source-backed change adds or removes a named product, changes exploitation or ransomware status, materially changes affected versions or remediation, identifies a campaign or victimology shift, or alters the executive action standard. Suppress routine no-change email. |
Related Intelligence and CARDS Records
PANDA CVE Watch Brief
Affected releases, KEV deadline, technical prerequisite, hunting questions, and remediation requirements.
Open productPANDA Flash Threat Brief
Executive and operational response to a FortiOS post-compromise persistence bypass.
Open productPANDA Flash Threat Brief
Detailed chain, attribution boundaries, incident response, malware, and campaign context.
Open productPANDA Flash Threat Brief
Plain-English business impact, vendor context, scenarios, and response guidance.
Open productRolling Intelligence
Official government notices, exploited technologies, actor campaigns, and deadlines across the same rolling window.
Open productRolling Intelligence
Carrier loss experience, policyholder technology risk, claims readiness, and accumulation context.
Open productCARDS
Searchable vulnerability records for the named CVEs and their connected actors, campaigns, and products.
Open productCARDS Actor Record
Connected actor intelligence, source-bound attribution context, behaviors, relationships, and defensive relevance.
Open productCARDS Actor Record
Connected actor intelligence, source-bound attribution context, behaviors, relationships, and defensive relevance.
Open productCARDS Campaign Record
Connected campaign intelligence, activity timeline, affected technologies, actors, techniques, and source boundaries.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productCARDS CVE / KEV Record
Connected vulnerability intelligence covering exploitation status, affected technology, remediation, and campaign relationships.
Open productRetained Sources and Claim Treatment
| # | Publisher | Published | Publication / Evidence | Why Used / Claim Treatment | Source |
|---|---|---|---|---|---|
| Source14 | PublisherGuidePoint Security | Published2026-07 | Publication / evidenceSource indexprimary research | Why used / claim treatmentQuarterly threat-research synthesis retained for ransomware-linked exploitation context, including Check Point CVE-2026-50751. Dataset and incident denominators remain separate from CISA and vendor records. | SourceGRIT Q2 2026 Ransomware and Cyber Threat Insights https://www.guidepointsecurity.com/wp-content/uploads/2026/07/GRIT_Q2_2026_Ransomware__Cyber_Threat_Insights_Report.pdf |
| Source20 | PublisherMITRE | PublishedCurrent definition checked 2026-07-28 | Publication / evidenceSource indexofficial | Why used / claim treatmentWeakness taxonomy retained to explain Fortinet's CWE-200 mapping. MITRE marks this broad category as discouraged for precise root-cause mapping; it describes unauthorized information exposure and does not independently establish exploitation, the underlying coding error, or local impact. | SourceCWE-200 — Exposure of Sensitive Information to an Unauthorized Actor https://cwe.mitre.org/data/definitions/200.html |