When a security researcher discovers a new vulnerability, they face a non-trivial decision: when, to whom, and how should this information be disclosed? This seemingly technical decision actually sits at the intersection of economics, ethics, and risk management, and the "right" answer depends heavily on context.

Full disclosure

Under this policy, a researcher immediately and publicly releases complete vulnerability details — sometimes including proof-of-concept (PoC) code — without prior notice to the vendor. The historical argument for this approach (tracing back to the "full-disclosure" movement of the 1990s) is that only immediate public pressure forces unwilling vendors to act. The cost is obvious: the gap between disclosure and patch release creates a public zero-day window that attackers can exploit immediately.

Coordinated/responsible disclosure

Under this model — today's dominant industry standard — a researcher first privately notifies the vendor and grants a fixed deadline (typically 90 days, per the common Google Project Zero standard) to fix the issue; public disclosure occurs only after a patch ships or the deadline expires. This model minimizes the risk of active exploitation but creates a serious economic problem: what incentive does the vendor have to meet the deadline if fixing the bug is costly and lower priority than shipping new features? The history of vulnerability disclosure is full of cases where vendors ignored the 90-day window until public disclosure created real media pressure.

The bug bounty market: an economic solution

Bug bounty programs (like HackerOne and Bugcrowd) address this by introducing a direct economic incentive: researchers receive financial rewards for responsible reporting. This creates a two-sided market in which a vulnerability's value (based on severity and target reach) gets priced. But this market creates its own new problem: the black market for zero-days (run by brokers like Zerodium) often offers far higher prices than official bug bounties, especially for vulnerabilities with surveillance or military applications. This creates a "price competition" in which legitimate bug bounty programs must compete against actors with an entirely different incentive — exploitation rather than remediation.

Why this isn't purely a technical problem

Choosing a disclosure policy ultimately comes down to balancing risks: the risk of active exploitation against the risk of vendor indifference against the researcher's economic incentive. No single policy is optimal across all contexts — a vulnerability in a patient-connected medical device carries entirely different considerations than a bug in a personal blog.

Conclusion

Vulnerability disclosure is a multidimensional decision in which a purely technical understanding of a bug is not enough; a responsible security researcher must also understand the economic incentives of every actor involved — the vendor, end users, and the competing black market.