Who it is for
Vulnerability management, release engineering and maintainer communities in open-source and enterprise software.
Why now
Three independent signals in one window: exploit probes reported within ten minutes of a public patch hint with CVE assignment slowing to weeks; a record 974-fix Patch Tuesday where the stated operational constraint is third-party compatibility testing and out-of-hours deployment, not fix availability; and a job posting seeking a volunteer senior maintainer with CVE embargo patching, SBOM production and on-call obligations for $0. A year ago the binding constraint was discovery and packaging; the constraint has moved to validation, deployment coverage and maintainer labor supply, which no embargo policy addresses.
What would kill it
Evidence that CVE assignment latency falls back to days and that AI-driven exploit probing is anecdotal rather than a measurable change in time-to-exploitation after public patch hints, which would restore the embargo as a workable assumption.