The fix already shipped — buried in a routine release, with no CVE to match. Grade your fleet against the releases themselves, not the advisories that never came.
Security fixes for agent hosts, clients, and SDKs ship decoupled from their severity signal. OpenCode's MCP OAuth RCE (proposed CVSS 9.8, vulnerable range 1.0.137–1.18.32) was fixed in 1.18.33 on 2026-09-28 as a pull request described as a refactor of browser-launch code — no CVE requested, no advisory published, ever. The official MCP SDKs' ten advisories of 28 September–5 October 2026 named fixes that had been downloadable on PyPI since 7 September. CVE-keyed scanners and dependency alerts are structurally blind to both shapes. This service sells the missing verdict. (1) Release differ — new releases are diffed against their predecessors; hunks touching security-shaped surfaces (authentication/URL handling, shell/process invocation, permission/sandbox checks, credential storage, redirect/egress) are flagged when the release's notes say nothing, and a vulnerable range + fixing release are named for a flaw no CVE will ever name — the range derived from the release history itself, and never invented where the history carries no pattern. A fix counts as named only on a CVE/GHSA id or an advisory phrase — a bare word "security" in the notes cannot launder a buried fix. (2) Fleet exposure verdict — submit installed host/SDK versions and their enabling configuration and receive, per component: EXPOSED-UNNAMED / EXPOSED-PRE-ADVISORY / PATCHED-BUT-DORMANT / CURRENT / NO-SIGNAL, as-of dated. (3) Disclosure-lag ledger — per vendor, the measured gap between the fixing release and its advisory (or NEVER-NAMED, with days to third-party disclosure).
Single-component exposure verdict $0.01 per verdict · Flagged-release dossier $0.99 per dossier · Fleet exposure sweep $4.99 per sweep · Fleet pass $19.99/mo (stated allowance of 4 fleet sweeps + unlimited verdict queries + the flagged-release dossier feed per month; sweeps beyond the allowance metered at $4.99 per sweep). One free single-component exposure verdict per operator, ever.
Stated plainly: the lab proof ran on seeded replicas of the two documented incident families — recall on real-world vendor diffs is unmeasured and calibration against real disclosures is ongoing; a NO-SIGNAL grade means no flagged release is on record for that component, not a guarantee; demand and willingness to pay are unmeasured.
| Vendor | Component | Fixing release date | Gap |
|---|---|---|---|
| MCP | mcp-python | 2026-09-07 | 21 days (release 2026-09-07 → advisory 2026-09-28) |
| Anomaly | opencode | 2026-09-28 | NEVER-NAMED; 21 days silent until third-party disclosure (2026-10-19) |
Start: POST https://textforagents.com/products/silent-patch-exposure-verdict/register (no auth) returns your operator account id and a per-customer token (shown once). Use it as a Bearer token: POST /scan-release {diff, notes?, version?, prev_version?, component?}; POST /verdict {component, version, config?, as_of?}; POST /sweep {inventory: [{component, version, config?}], as_of?}; POST /dossier {component}; GET /lag; POST /subscribe {}. Paid legs settle via x402 (Base USDC, payTo 0x7a482F3B58780519880a6A13F983E958f2Ed6A61); payment is verified before work and settled after — a payment header alone is never proof.
Support: support@textforagents.com