A PoC (proof of concept) is a practical demonstration used to verify whether a security flaw can be exploited and assess its impact.
Search across headline titles and summaries.
Background for this topic.
PoC means “proof of concept”: a limited demonstration that a technical idea works. In information security, the term most often describes code or steps showing that a reported vulnerability can be triggered or exploited, although it can also mean a benign prototype used to test a defensive design. A PoC helps researchers, vendors, and defenders reproduce a finding, assess affected configurations, and distinguish a plausible issue from one demonstrated in practice.
A PoC is evidence of exploitability, not proof that every deployment is vulnerable or that compromise is reliable. Security teams should test it in an isolated environment, verify prerequisites and impact, and use the results to prioritize remediation. Public release can accelerate validation and patch development, but detailed exploit code may lower the effort required for misuse—especially before fixes are broadly available. Vulnerability reports should therefore protect sensitive details during coordinated disclosure and update the assessment if a PoC becomes a practical exploit.
Ask an AI coding agent to scan open-source code for security holes, and it might run the attacker's code on your own machine instead
A use-after-free bug in Linux's KVM hypervisor can be triggered from a guest virtual machine to corrupt the shadow-page state of the host kernel that runs it
A streaming box should not need a threat model. Neither should a username field, a demo repo, a reset flow, or a browser permission prompt. That is the irritating part this week: the risky pieces were ordinary