Runtime reachability and live-state reads: what they prove and what they miss
No standards body defines the term, so vendor documentation is the primary source. Endor Labs describes instrumented container reachability as embedding "a runtime sensor in your container image to record how your application uses the image in a real environment." Sysdig lists as a feature a focus on "the vulnerabilities tied to the packages loaded at runtime," and states that pipeline scans carry no runtime context, so a CI scan is a static snapshot while an agent on the node sees what runs.
In practice a sensor is installed in the image or on the node and the workload is exercised. Endor Labs suggests profiling in "a realistic environment, such as staging, that mirrors production traffic," or when you "already have integration or end-to-end tests and want reachability to reflect those tests." It runs through Kubernetes or Docker with the endorctl container scan command and the --os-reachability flag. The output sorts each finding by whether its package was seen in use. Findings in packages never loaded move down the queue; they are not deleted.
CVE-2026-53266 is an out-of-bounds write in the Linux ebtables SNAT target. The fix was committed to mainline on 1 Jun 2026, Red Hat's public date, and the kernel CNA published the CVE record on 25 Jun 2026. Backports shipped in kernels 5.10.259, 5.15.210, 6.1.176, 6.6.143, 6.12.94, 6.18.36 and 7.0.13. A version scan flags every host in the affected ranges, for example a host on 6.1.150, which lies in the 5.16 to before 6.1.176 range. The ledger record says the deciding facts are runtime ones: bridge netfilter and ebtables must be in use, with a rule using the snat target with ARP rewrite, and the attacker needs local low-privileged access. Whether a local user can install such a rule depends on capabilities such as CAP_NET_ADMIN, which the advisory does not state. CISA listed the flaw on 18 Sep 2026 with a due date of 21 Sep 2026; the ledger takes that listing as the first dated report of exploitation, so exploitation may have begun earlier. Its EPSS score on 18 Nov 2026 was 0.00934. The reads that settle it are ebtables -t nat -L as root, looking for -j snat rules with --snat-arp, and lsmod | grep -E 'ebtable_nat|ebt_snat'. On a host where the module is not loaded and no such rule exists, the version finding over-reports.
The method gives a wrong 'not in use' when the sensor watched the wrong period. A library loaded by a quarterly reconciliation job is absent from a one-week profile, and the finding is demoted until the job runs. Endor Labs ties its result to the profiled usage, so a staging run that mirrors only part of production traffic yields a partial answer. The reverse error is a library that is loaded but only reachable by a caller who never meets an attacker, which loaded-at-runtime evidence cannot tell apart from one that can be attacked.
The other six of the seven entries turn on the state of a running service or host rather than on loaded packages, and a package sensor does not report these. They are answered by reading the live system. The table gives the read that settles each.
The live-state reads
| Entry | The state that decides | The read that settles it |
|---|---|---|
| Langflow, CVE-2026-9198 | The effective LANGFLOW_AUTO_LOGIN value and the listening address | env | grep LANGFLOW_AUTO_LOGIN, then ss -ltnp | grep -i langflow. An unset value on 1.10.0 or earlier counts as enabled; 1.10.1 is the first fixed release. |
| LiteLLM, CVE-2026-59822 | The MCP server authentication type and whether the /mcp/ route is reachable | grep -n -A8 mcp_servers config.yaml for the auth_type of each server, then curl -s -o /dev/null -w '%{http_code}\n' https://PROXY_HOST/mcp/ from an untrusted network. A 401 or 403 means the route is reachable and rejects anonymous callers. |
| MLflow, CVE-2026-64849 | Whether the webhooks API is open without authentication and what the server can reach outbound | ps -ef | grep 'mlflow server' and look for --app-name basic-auth; without it the API is open. Then ss -ltnp | grep -i mlflow for the bind address. |
| Linux kernel, CVE-2026-46300 | Whether the ESP modules can load and whether unprivileged namespaces are allowed | lsmod | grep -E 'esp4|esp6' and sysctl user.max_user_namespaces. Red Hat documents the module block and the namespace setting as separate mitigations, so a host is exposed only while both are open. |
| SharePoint, CVE-2026-65660 | The farm build and whether any site allows anonymous viewing | (Get-SPFarm).BuildVersion in the SharePoint Management Shell, compared with 16.0.5565.1001 (2016), 16.0.10417.20198 (2019) and 16.0.19725.20522 (Subscription Edition). Anonymous access: Central Administration > Application Management > Manage web applications > Authentication Providers. |
| WordPress, CVE-2026-119977 | Whether a core upgrade runs and whether the staging path answers over HTTP | curl -sI https://your-site.example/wp-content/upgrade/ from outside the network: 200 or a directory listing means reachable, 403 or 404 means the condition is removed. During an upgrade, ls -la wp-content/upgrade/ shows a package-named folder with no random suffix when the unfixed code ran. |
The SharePoint build read counts as a runtime read because Get-SPFarm asks the running farm which build it reports, and the anonymous-access setting is read from its live web applications. A scan of installer files or a package list can show neither.
A worked sensor result, with constructed numbers
The figures are constructed to show the shape of a result; they are not output from a product. Two bridge hosts run kernel 6.1.150, inside the affected range for CVE-2026-53266, so a version scan flags both. A sensor profiles each for 14 days. On host A, 380 of 1,040 installed packages were loaded, the ebtables modules never loaded, and no ebtables rule exists; the finding is demoted to not in use, with the window and the module list recorded. On host B the bridge netfilter and ebt_snat modules were loaded and a nat rule with the --snat-arp option exists; the finding stays at the front of the queue. Host A's finding is demoted, not deleted, so a rule added after day 14 would show on the next profile.
Who sets the window and what it leaves
- Platform or site reliability owner, with the application owner: sets the observation window so that it covers the longest job cycle of the workload (a monthly or quarterly job needs a window that includes it). Record: window start and end, workloads covered, and the sensor version.
- Security analyst: reviews each demotion before the finding's deadline and checks the window against the job calendar. Record: reviewer, date and the window used.
- Application owner: reports any change that adds code paths, such as a new job or a new rule, which restarts the profile. Record: the change ticket linked to the finding.
Ledger entries it settles
- CVE-2026-119977: WordPress Coredisclosed 28 Oct 2026
- CVE-2026-46300: Linux Kerneldisclosed 13 May 2026
- CVE-2026-53266: Linux kerneldisclosed 1 Jun 2026
- CVE-2026-59822: BerriAI LiteLLMdisclosed 8 Jul 2026
- CVE-2026-64849: MLflow Tracking Serverdisclosed 17 Aug 2026
- CVE-2026-65660: Microsoft SharePoint Serverdisclosed 11 Aug 2026
- CVE-2026-9198: IBM Langflow OSSdisclosed 2 Jul 2026
Related pages
Sources
- Endor Labs instrumented container reachability, read 19 Nov 2026
- Sysdig vulnerability management documentation, read 19 Nov 2026
- CISA KEV JSON feed, version 2026.11.18, read 19 Nov 2026
- FIRST EPSS API for CVE-2026-53266, EPSS date 18 Nov 2026, read 19 Nov 2026
- NVD record for CVE-2026-53266, read 10 Nov 2026
- Upwind home page (vendor claim), read 10 Nov 2026
- Oligo home page (vendor claim), read 10 Nov 2026
- Onit platform page (vendor claim), read 10 Nov 2026
- Zafran home page (vendor claim), read 10 Nov 2026
- Astelia platform page (vendor claim), read 10 Nov 2026
Last reviewed 19 Nov 2026.