# Reachability analysis in four questions: which of your findings can be exploited

REFERENCE, read 19 Nov 2026

**The short answer.** Reachability analysis checks whether vulnerable code is called and whether the service can be reached where you run it. The four-question tool on this page turns your answers into the method that settles a finding. The ledger covers 37 headline CVEs disclosed from 9 Apr to 5 Nov 2026, and 33 are in CISA KEV.

## Walk one finding through four questions

Four questions, each answered yes, no or not sure: (1) Is the vulnerable code called? (2) Can the service be reached? (3) Is a control in front of it? (4) Is exploitation known?

Start from your own finding or from one of the 37 ledger entries. Picking an entry fills the answers from its record: exploitation known from its KEV and first-exploitation dates, the question its settling method decides left as not sure, and the others set as exposed. An unanswered question counts as not sure; with all four open, Rule 4 sends the finding to Agent investigation.

The tool opens on CVE-2026-123158 (OpenBSD OpenSSH, disclosed 5 Nov 2026, D+2), preselected in the entry list. Its four answers: (1) Is the vulnerable code called? not sure; (2) Can the service be reached? yes; (3) Is a control in front of it? no; (4) Is exploitation known? yes. Rule 5 applies: Reached: yes, no control in front, and the code question is the only one not sure. Method that settles it: [Static reachability and configuration reads](/methods/static-reachability/), or [runtime reachability and live-state reads](/methods/runtime-reachability/) on a running workload. The ledger records it for this entry because: Exposure rests on build and configuration facts that a read of the package and config settles: musl, no PAM, password authentication on, and a * account next to a hashed account. Those are static properties of the host, so a scan of the build and /etc/shadow gives the answer before any attack arrives, and a severity score or exploit feed cannot say which hosts meet all of them.

- **What it proves:** That a call path exists from your code to the vulnerable function, shown step by step where one is found, and that the version, packaging and configuration facts in the CVE record hold or fail in the build.
- **What it misses:** Network exposure, identity, controls, whether the code is deployed and running, and any setting changed after the read.
- **Evidence to keep:** The call path from your code to the vulnerable function, with the path shown; or, from a running workload, whether the vulnerable package or function was loaded or executed, with the observation window. Static reachability reads code and build facts; runtime reachability reads a running workload and does not see code paths left unexercised during the window.
- **Ledger:** 14 of 37 ledger entries settle on it, newest: [CVE-2026-123158](/ledger/cve-2026-123158/) (5 Nov 2026, D+2), [CVE-2026-19868](/ledger/cve-2026-19868/) (5 Nov 2026, D+1), [CVE-2026-76418](/ledger/cve-2026-76418/) (28 Oct 2026, D+0), [CVE-2026-111497](/ledger/cve-2026-111497/) (21 Oct 2026, D+5).


## Days from disclosure to first exploitation

All 37 ledger entries by days from disclosure to first observed exploitation: 2 before disclosure, 10 on the day, 21 after, and 4 with no dated report. The median is 2 days.


## The ledger, all 37 entries

| Disclosed | CVE | Product | Days | Code called | Reached | Control | Known | Settled by |
|---|---|---|---|---|---|---|---|---|
| 5 Nov 2026 | [CVE-2026-123158](/ledger/cve-2026-123158/) | OpenBSD OpenSSH | D+2 | open | yes | no | yes | Static reachability |
| 5 Nov 2026 | [CVE-2026-19868](/ledger/cve-2026-19868/) | SonicWall SonicOS SSLVPN | D+1 | open | yes | no | yes | Static reachability |
| 28 Oct 2026 | [CVE-2026-119977](/ledger/cve-2026-119977/) | WordPress Core | D+6 | open | yes | no | yes | Runtime reachability |
| 28 Oct 2026 | [CVE-2026-76418](/ledger/cve-2026-76418/) | Cisco Secure Firewall ASA and FTD | D+0 | open | yes | no | yes | Static reachability |
| 21 Oct 2026 | [CVE-2026-109618](/ledger/cve-2026-109618/) | PHP Group PHP | D+0 | yes | open | no | yes | Attack-path analysis |
| 21 Oct 2026 | [CVE-2026-109619](/ledger/cve-2026-109619/) | PHP Group PHP | D+5 | yes | open | no | yes | Attack-path analysis |
| 21 Oct 2026 | [CVE-2026-111497](/ledger/cve-2026-111497/) | Node.js Brotli decoder | D+5 | open | yes | no | yes | Static reachability |
| 15 Oct 2026 | [CVE-2026-102764](/ledger/cve-2026-102764/) | BeyondTrust Remote Support | D-47 | open | yes | no | yes | Static reachability |
| 14 Oct 2026 | [CVE-2026-0322](/ledger/cve-2026-0322/) | Palo Alto Networks PAN-OS | D+0 | yes | open | no | yes | Attack-path analysis |
| 12 Oct 2026 | [CVE-2026-97229](/ledger/cve-2026-97229/) | GitLab CE/EE | D+1 | yes | open | no | yes | Attack-path analysis |
| 5 Oct 2026 | [CVE-2026-21589](/ledger/cve-2026-21589/) | Atlassian Data Center products | D+10 | open | yes | no | yes | Static reachability |
| 3 Oct 2026 | [CVE-2026-88779](/ledger/cve-2026-88779/) | Citrix NetScaler ADC and Gateway | D+1 | open | yes | no | yes | Static reachability |
| 1 Oct 2026 | [CVE-2026-104286](/ledger/cve-2026-104286/) | Fortinet FortiMail | D+0 | open | yes | no | yes | Static reachability |
| 30 Sep 2026 | [CVE-2026-94545](/ledger/cve-2026-94545/) | Vercel Satori and Next.js | no date | open | yes | no | no | Static reachability |
| 22 Sep 2026 | [CVE-2026-94127](/ledger/cve-2026-94127/) | F5 BIG-IP APM | D+0 | open | yes | no | yes | Static reachability |
| 16 Sep 2026 | [CVE-2026-76460](/ledger/cve-2026-76460/) | Cisco Identity Services Engine | D+0 | yes | open | no | yes | Attack-path analysis |
| 8 Sep 2026 | [CVE-2026-81963](/ledger/cve-2026-81963/) | Microsoft Windows Update Stack | D+0 | yes | open | no | yes | Attack-path analysis |
| 8 Sep 2026 | CVE-2026-85880 | Microsoft Windows ALPC | D+0 | yes | open | no | yes | Attack-path analysis |
| 7 Sep 2026 | [CVE-2026-75650](/ledger/cve-2026-75650/) | Adobe Commerce and Magento Open Source | D-3 | yes | yes | no | yes | Known-exploited lists |
| 4 Sep 2026 | [CVE-2026-87491](/ledger/cve-2026-87491/) | Google Chromium V8 | D+0 | open | open | open | yes | Agent investigation |
| 3 Sep 2026 | [CVE-2026-84869](/ledger/cve-2026-84869/) | ConnectWise ScreenConnect | D+7 | open | open | open | yes | Agent investigation |
| 28 Aug 2026 | [CVE-2026-82329](/ledger/cve-2026-82329/) | JFrog Artifactory | D+4 | open | open | open | yes | Agent investigation |
| 26 Aug 2026 | [CVE-2026-80521](/ledger/cve-2026-80521/) | Linux kernel | no date | yes | open | no | no | Attack-path analysis |
| 25 Aug 2026 | [CVE-2026-75604](/ledger/cve-2026-75604/) | Vercel Next.js | no date | open | yes | no | no | Static reachability |
| 19 Aug 2026 | [CVE-2026-19490](/ledger/cve-2026-19490/) | Citrix NetScaler ADC and Gateway | D+21 | open | yes | no | yes | Static reachability |
| 17 Aug 2026 | [CVE-2026-64849](/ledger/cve-2026-64849/) | MLflow Tracking Server | D+2 | open | yes | no | yes | Runtime reachability |
| 12 Aug 2026 | [CVE-2026-42018](/ledger/cve-2026-42018/) | JFrog Artifactory | D+3 | yes | open | no | yes | Attack-path analysis |
| 11 Aug 2026 | [CVE-2026-65660](/ledger/cve-2026-65660/) | Microsoft SharePoint Server | D+44 | open | yes | no | yes | Runtime reachability |
| 11 Aug 2026 | [CVE-2026-68820](/ledger/cve-2026-68820/) | Microsoft Windows AFD for WinSock | D+0 | yes | open | no | yes | Attack-path analysis |
| 29 Jul 2026 | [CVE-2026-41709](/ledger/cve-2026-41709/) | Broadcom VMware ESX | D+91 | yes | yes | no | yes | Known-exploited lists |
| 27 Jul 2026 | [CVE-2026-42016](/ledger/cve-2026-42016/) | JFrog Artifactory | D+19 | yes | open | no | yes | Attack-path analysis |
| 21 Jul 2026 | [CVE-2026-16723](/ledger/cve-2026-16723/) | Alibaba fastjson 1.x | no date | open | yes | no | no | Static reachability |
| 8 Jul 2026 | [CVE-2026-59822](/ledger/cve-2026-59822/) | BerriAI LiteLLM | D+50 | open | yes | no | yes | Runtime reachability |
| 2 Jul 2026 | [CVE-2026-9198](/ledger/cve-2026-9198/) | IBM Langflow OSS | D+15 | open | yes | no | yes | Runtime reachability |
| 1 Jun 2026 | [CVE-2026-53266](/ledger/cve-2026-53266/) | Linux kernel | D+109 | open | yes | no | yes | Runtime reachability |
| 13 May 2026 | [CVE-2026-46300](/ledger/cve-2026-46300/) | Linux Kernel | D+1 | open | yes | no | yes | Runtime reachability |
| 9 Apr 2026 | [CVE-2026-34486](/ledger/cve-2026-34486/) | Apache Software Foundation Apache Tomcat | D+15 | open | yes | no | yes | Static reachability |

Downloads: [ledger.csv](/datasets/ledger.csv), [ledger.json](/datasets/ledger.json), CC BY 4.0.


## The Methods Matrix at a glance

A filled square means the method's proves text, as published on its page, speaks to the question; an empty one means it does not. An exploit-prediction score estimates how likely exploitation is across all deployments, so it speaks to the fourth question only in general, not for your environment.

| Method | Code | Reach | Control | Known |
| --- | --- | --- | --- | --- |
| Agent investigation | proves it | proves it | proves it | no |
| Attack-path analysis | no | proves it | proves it | no |
| [EPSS exploit prediction](/methods/exploit-prediction/) | no | no | no | proves it |
| [Known-exploited lists](/methods/known-exploited/) | no | no | no | proves it |
| [Runtime reachability and live-state reads](/methods/runtime-reachability/) | proves it | no | no | no |
| [Severity scores](/methods/severity-score/) | no | no | no | no |
| [Static reachability and configuration reads](/methods/static-reachability/) | proves it | no | no | no |

Alphabetical by method name. Each mark is read from the method's proves text.

## How the answers map to a method

No standards body defines reachability analysis, so the primary source is vendor documentation. Snyk describes it as "identifying whether your application is calling a code element (for example, functions, classes, modules, and more) related to the vulnerability" ([Snyk reachability analysis documentation](https://docs.snyk.io/manage-risk/prioritize-issues-for-fixing/reachability-analysis), read 19 Nov 2026). That answers the code question only. It gives the wrong answer when the call graph is incomplete, because the same page states that a NO PATH FOUND status does not mean the vulnerability is completely unreachable. It also says nothing about a server compromised before it was patched, as with CVE-2026-82329.

The rules are read from the methods' own text and applied in order, and the first rule that matches applies. A "no" to reach, a "yes" to a control or a "no" to the code question rules exposure out, so the method is the one whose proves text produces that answer. Open questions go to the method that proves them; two or more open questions go to agent investigation, the one method whose proves text covers configuration, code, controls and network path. The fourth answer is read only when the finding is exposed, because known exploitation changes urgency, not exposure. The combinations column adds up to 81.

| Rule | When the answers are | Method that settles it | Combinations of 81 |
| --- | --- | --- | --- |
| Rule 1 | Can the service be reached: no. The other answers do not change the method. | Attack-path analysis | 27 |
| Rule 2 | Reached: yes or not sure, and a control is in front of it: yes. | Agent investigation | 18 |
| Rule 3 | Reached: yes or not sure, no control confirmed, and the code is called: no. | [Static reachability and configuration reads](/methods/static-reachability/) | 12 |
| Rule 4 | Nothing above rules it out, and two or three of the first three answers are not sure. | Agent investigation | 12 |
| Rule 5 | Reached: yes, no control in front, and the code question is the only one not sure. | [Static reachability and configuration reads](/methods/static-reachability/), or [runtime reachability and live-state reads](/methods/runtime-reachability/) on a running workload | 3 |
| Rule 6 | The code is called, and only the reach question or only the control question is not sure. | Attack-path analysis | 6 |
| Rule 7 | Called: yes, reached: yes, control: no, and exploitation known: yes or not sure. | [Known-exploited lists](/methods/known-exploited/) | 2 |
| Rule 8 | Called: yes, reached: yes, control: no, and exploitation known: no. | [EPSS exploit prediction](/methods/exploit-prediction/) | 1 |

Three answers to four questions give 81 combinations; each one matches exactly one rule. Method text read 19 Nov 2026.

## Sources

- Snyk reachability analysis documentation: definition of reachability analysis and the NO PATH FOUND limit: https://docs.snyk.io/manage-risk/prioritize-issues-for-fixing/reachability-analysis (read 19 Nov 2026)
- CVE-2026-123158: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-123158 (read 19 Nov 2026)
- CVE-2026-123158: CISA KEV catalog entry, added 9 Nov 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-123158 (read 19 Nov 2026)
- CVE-2026-123158: first exploitation, GreyNoise event page and timeline: https://sshole.events.greynoise.io/ (read 19 Nov 2026)
- CVE-2026-19868: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-19868 (read 19 Nov 2026)
- CVE-2026-19868: CISA KEV catalog entry, added 6 Nov 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-19868 (read 19 Nov 2026)
- CVE-2026-119977: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-119977 (read 19 Nov 2026)
- CVE-2026-119977: CISA KEV catalog entry, added 3 Nov 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-119977 (read 19 Nov 2026)
- CVE-2026-76418: NVD record; the first-exploitation date, 28 Oct 2026, comes from this record: https://nvd.nist.gov/vuln/detail/CVE-2026-76418 (read 19 Nov 2026)
- CVE-2026-76418: CISA KEV catalog entry, added 29 Oct 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-76418 (read 19 Nov 2026)
- CVE-2026-109618: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-109618 (read 19 Nov 2026)
- CVE-2026-109618: CISA KEV catalog entry, added 26 Oct 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-109618 (read 19 Nov 2026)
- CVE-2026-109618: first exploitation, Fastly report on PHP2Shell exploitation, disclosure timeline and indicators: https://www.fastly.com/blog/how-fastly-detected-and-built-a-coordinated-response-to-php2shell (read 19 Nov 2026)
- CVE-2026-109619: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-109619 (read 19 Nov 2026)
- CVE-2026-109619: CISA KEV catalog entry, added 26 Oct 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-109619 (read 19 Nov 2026)
- CVE-2026-111497: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-111497 (read 19 Nov 2026)
- CVE-2026-111497: CISA KEV catalog entry, added 27 Oct 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-111497 (read 19 Nov 2026)
- CVE-2026-111497: first exploitation, ELLIO research on exploitation and affected builds: https://ellio.tech/en/blog/node2shell-cve-2026-111497-rce-on-stock-nodejs-builds/ (read 19 Nov 2026)
- CVE-2026-102764: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-102764 (read 19 Nov 2026)
- CVE-2026-102764: CISA KEV catalog entry, added 16 Oct 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-102764 (read 19 Nov 2026)
- CVE-2026-102764: first exploitation, BeyondTrust blog on ARMORY CASTLE and BT26-05: https://www.beyondtrust.com/blog/entry/bt26-05 (read 19 Nov 2026)
- CVE-2026-0322: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-0322 (read 19 Nov 2026)
- CVE-2026-0322: CISA KEV catalog entry, added 14 Oct 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-0322 (read 19 Nov 2026)
- CVE-2026-97229: NVD record; the first-exploitation date, 13 Oct 2026, comes from this record: https://nvd.nist.gov/vuln/detail/CVE-2026-97229 (read 19 Nov 2026)
- CVE-2026-97229: CISA KEV catalog entry, added 29 Oct 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-97229 (read 19 Nov 2026)
- CVE-2026-21589: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-21589 (read 19 Nov 2026)
- CVE-2026-21589: CISA KEV catalog entry, added 15 Oct 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-21589 (read 19 Nov 2026)
- CVE-2026-88779: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-88779 (read 19 Nov 2026)
- CVE-2026-88779: CISA KEV catalog entry, added 4 Oct 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-88779 (read 19 Nov 2026)
- CVE-2026-104286: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-104286 (read 19 Nov 2026)
- CVE-2026-104286: CISA KEV catalog entry, added 1 Oct 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-104286 (read 19 Nov 2026)
- CVE-2026-94545: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-94545 (read 19 Nov 2026)
- CVE-2026-94127: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-94127 (read 19 Nov 2026)
- CVE-2026-94127: CISA KEV catalog entry, added 22 Sep 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-94127 (read 19 Nov 2026)
- CVE-2026-76460: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-76460 (read 19 Nov 2026)
- CVE-2026-76460: CISA KEV catalog entry, added 16 Sep 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-76460 (read 19 Nov 2026)
- CVE-2026-81963: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-81963 (read 19 Nov 2026)
- CVE-2026-81963: CISA KEV catalog entry, added 8 Sep 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-81963 (read 19 Nov 2026)
- CVE-2026-85880: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-85880 (read 19 Nov 2026)
- CVE-2026-85880: CISA KEV catalog entry, added 8 Sep 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-85880 (read 19 Nov 2026)
- CVE-2026-75650: NVD record carrying Adobe's advisory data for APSB26-146 (affected versions, hotfix, CVSS): https://nvd.nist.gov/vuln/detail/CVE-2026-75650 (read 19 Nov 2026)
- CVE-2026-75650: CISA KEV catalog entry, added 8 Sep 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-75650 (read 19 Nov 2026)
- CVE-2026-75650: first exploitation, Sansec research: StyleSmuggler 0-day (hotfix details, versions tested, indicators, timeline): https://sansec.io/research/stylesmuggler-0day (read 19 Nov 2026)
- CVE-2026-87491: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-87491 (read 19 Nov 2026)
- CVE-2026-87491: CISA KEV catalog entry, added 9 Sep 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-87491 (read 19 Nov 2026)
- CVE-2026-87491: first exploitation, Microsoft Edge security release notes: https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnotes-security (read 19 Nov 2026)
- CVE-2026-84869: NVD record; the first-exploitation date, 10 Sep 2026, comes from this record: https://nvd.nist.gov/vuln/detail/CVE-2026-84869 (read 19 Nov 2026)
- CVE-2026-84869: CISA KEV catalog entry, added 11 Sep 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-84869 (read 19 Nov 2026)
- CVE-2026-82329: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-82329 (read 19 Nov 2026)
- CVE-2026-82329: Wiz Research report, which confirmed successful exploitation between 1 and 8 Sep 2026, so servers were compromised before they were patched; also the first-exploitation source for CVE-2026-42018, 15 Aug 2026; also the first-exploitation source for CVE-2026-42016, 15 Aug 2026: https://www.wiz.io/blog/artifactory-under-attack-in-the-wild-exploitation-of-cve-2026-42016-cve-2026-4201 (read 19 Nov 2026)
- CVE-2026-82329: CISA KEV catalog entry, added 2 Sep 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-82329 (read 19 Nov 2026)
- CVE-2026-82329: first exploitation, Fastly Security Research report, 3 Sep 2026: https://www.fastly.com/blog/cve-2026-82329-jfrog-artifactory-authentication-bypass-exploitation-activity (read 19 Nov 2026)
- CVE-2026-80521: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-80521 (read 19 Nov 2026)
- CVE-2026-75604: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-75604 (read 19 Nov 2026)
- CVE-2026-19490: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-19490 (read 19 Nov 2026)
- CVE-2026-19490: CISA KEV catalog entry, added 9 Sep 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-19490 (read 19 Nov 2026)
- CVE-2026-64849: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-64849 (read 19 Nov 2026)
- CVE-2026-64849: CISA KEV catalog entry, added 19 Aug 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849 (read 19 Nov 2026)
- CVE-2026-42018: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-42018 (read 19 Nov 2026)
- CVE-2026-42018: CISA KEV catalog entry, added 11 Sep 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-42018 (read 19 Nov 2026)
- CVE-2026-65660: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-65660 (read 19 Nov 2026)
- CVE-2026-65660: CISA KEV catalog entry, added 25 Sep 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-65660 (read 19 Nov 2026)
- CVE-2026-65660: first exploitation, Previdian research on exploitation attempts: https://blog.previdian.com/cve-2026-65660-previdian-observes-two-stage-sharepoint-exploitation-attempts/ (read 19 Nov 2026)
- CVE-2026-68820: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-68820 (read 19 Nov 2026)
- CVE-2026-68820: CISA KEV catalog entry, added 11 Aug 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-68820 (read 19 Nov 2026)
- CVE-2026-41709: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-41709 (read 19 Nov 2026)
- CVE-2026-41709: CISA KEV catalog entry, added 28 Oct 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-41709 (read 19 Nov 2026)
- CVE-2026-42016: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-42016 (read 19 Nov 2026)
- CVE-2026-42016: CISA KEV catalog entry, added 11 Sep 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-42016 (read 19 Nov 2026)
- CVE-2026-16723: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-16723 (read 19 Nov 2026)
- CVE-2026-59822: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-59822 (read 19 Nov 2026)
- CVE-2026-59822: CISA KEV catalog entry, added 2 Sep 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-59822 (read 19 Nov 2026)
- CVE-2026-59822: first exploitation, Wiz Research honeypot report: https://www.wiz.io/blog/ai-infrastructure-honeypot (read 19 Nov 2026)
- CVE-2026-9198: NVD record; the first-exploitation date, 17 Jul 2026, comes from this record: https://nvd.nist.gov/vuln/detail/CVE-2026-9198 (read 19 Nov 2026)
- CVE-2026-9198: CISA KEV catalog entry, added 4 Aug 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-9198 (read 19 Nov 2026)
- CVE-2026-53266: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-53266 (read 19 Nov 2026)
- CVE-2026-53266: CISA KEV catalog entry, added 18 Sep 2026; the first-exploitation date is this KEV date added: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-53266 (read 19 Nov 2026)
- CVE-2026-46300: NVD record; the first-exploitation date, 14 May 2026, comes from this record: https://nvd.nist.gov/vuln/detail/CVE-2026-46300 (read 19 Nov 2026)
- CVE-2026-46300: CISA KEV catalog entry, added 28 Oct 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-46300 (read 19 Nov 2026)
- CVE-2026-34486: NVD record: https://nvd.nist.gov/vuln/detail/CVE-2026-34486 (read 19 Nov 2026)
- CVE-2026-34486: CISA KEV catalog entry, added 4 Aug 2026: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-34486 (read 19 Nov 2026)
- CVE-2026-34486: first exploitation, SOCRadar research on the SNOWLIGHT campaign (exploitation and indicators): https://socradar.io/blog/snowlight-government-chinese-campaign/ (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/
