Spektion (@spektion) header
Spektion (@spektion) profile picture

Endpoint vulnerability management beyond CVEs. Which CVEs are exploitable on each machine, what never gets a CVE, and a control when there is no patch.

Dripping Springs, TX, USA
Joined December 2021
Photo by Spektion (@spektion)Photo by Spektion (@spektion)Photo by Spektion (@spektion)Photo by Spektion (@spektion)Photo by Spektion (@spektion)Photo by Spektion (@spektion)Photo by Spektion (@spektion)Photo by Spektion (@spektion)Photo by Spektion (@spektion)Photo by Spektion (@spektion)
Both PaperCut CVE records published the fix as "24.1.10, 25.0.13, 26.0.5" in one field typed as semver. NVD resolved that into ranges ending at 24.1.9, 25.0.12, 26.0.4. One release short. A tool that takes those ranges as written calls a vulnerable server fixed.
1
63
Microsoft's researchers put the median patch on a Windows workstation at "about two weeks." On a network appliance: "beyond a year." A compensating control sized for the first number ends up doing the job of the second.
1
2
The tracker ritual: mark the finding mitigated, and it leaves the patch queue. Open findings run on an SLA clock. Risk exceptions expire. Mitigated does neither, so when the vendor ships the fix, the queue no longer lists the appliance.
1
1
Kirk Havens of NielsenIQ expects the "aha moment" for standards bodies to come from breaches through a vulnerability teams "didn't even have the time to scan for." Requirements move on a committee calendar. Exploitation is not on it.
4
Fix first. Make a plan. Assign it to the owners. The third ask is where a patch list meets its first objection. The agent in this clip files both tickets with Spektion's runtime evidence: whether the software ran, at what privilege, and whether it was listening.
1
4
N-able shipped an N-central hotfix two days after Sean Bales published 33 flaws, then a second six days later. Both tell customers to upgrade their Agents and Probes. That instruction assumes you know you are a customer. The Agent a former MSP left behind did not get the memo.
1
7
The only CVE Microsoft flagged as exploited in its November 10 release is rated Moderate: CVE-2026-124194 in Outlook, CVSS 6.5. Microsoft rated 63 others Critical. None of the 63 carries the exploited flag.
1
1
30
Two questions, two kinds of evidence. Exploited anywhere? Microsoft's flag and CISA's KEV listing answered that, and a Moderate went to the front. Requires action here? That takes runtime evidence: where the software runs, at what privilege, with what network exposure.
1
4
Microsoft rated 63 CVEs Critical on November 10. It flagged one CVE as exploited: CVE-2026-124194 in Outlook, rated Moderate. A queue sorted by severity reaches it after all 63. CISA wants it fixed by November 24. The severity column does not mention that.
1
63
M-Trends 2026 estimates mean time to exploit at minus 7 days. A patch SLA can read 100% on time for a vulnerability attackers used before the patch existed. The report is accurate. It starts counting at release.
9
A 30-minute VM self-test: count what your top vendor fixed in its last three releases against what your scanner flagged. Joe Silva adds a third column: how that software behaves on your hosts. A scan-first program fills it with a version string. lnkd.in/p/enrvgnys
5
TrueConf patched an unauthenticated server bug in June. Kaspersky says attackers were exploiting it by July. The CVE came in August. For a scan-first program, that bug did not exist for about two months, including the month someone was exploiting it. spektion.com/articles/disclo…
53
Approval fatigue has a file path. Click "Yes, and don't ask again" in Claude Code and it saves the exact command, secret included, to .claude/settings.local.json. 215 public copies on GitHub held secrets two popular scanners both missed.
1
16
An unquoted service path under an elevated account gets filed under hardening. If a local user can write along that path, it is a privilege escalation with no CVE. Spektion's sensor observed the launch. The fix needs no vendor: quote the path, drop the privilege.
1
2
47
AI coding agents keep setting up MCP servers their maintainers archived. In the sessions researchers reviewed, 98% of deprecated-server setups traced to the model's training data.
2
12
→ The Puppeteer server is one of them. A prompt injection can turn it into remote code execution. Its maintainers archived it in May 2025 and say no fix will come. It and the three other high-severity flaws reported have no CVE.
1
30
Spektion's threat research lead sends vendors exploit proof, usually with video. Then he waits months. The accepted disclosure timeline is 90 to 120 days. The software stays in production for all of them.
1
1
51
Three vendor replies he reports: → The vendor doubts the component exists. → The vendor calls it a third party's responsibility. → The vendor says it is patched. He finds no CVE. Without a published CVE, a scanner has none to match.
1
22