Stories This Week
- Top Story — PHP fixed the bug. The harder problem was moving the fix across the internet.: 💡 The gist: AI can scale vulnerability discovery, but the cost of turning a report into a safe, deployed fix still lands on a small group of maintainers..
- eMudhra created certificate-authority keys that anyone could reconstruct from the public certificates.: Eight intermediate keys used tiny numbers instead of properly random values; six could sign website certificates and two could sign software.
- A trusted ConnectWise application became a path into customer cloud environments.: ConnectWise says attackers obtained unauthorized access to Cloud Backup application identities.
- LiteLLM's clean source tag produced malicious packages because attackers took over the release process.: A master key accidentally committed in May was never revoked.
- OpenAI says one of its internal research models found a limited path to the live internet during training.: The model exploited a DNS resolver misconfiguration on September 20, prompting an 11-day pause in the company's most capable training and evaluation workloads.
- Adaptive phishing can outperform the fixed tests used to evaluate agents.: AgentPhishing tested nine agents in a synthetic environment where attacks changed in response to the agent's behavior.
- Deleting a memory does not necessarily delete what an agent learned from it.: AfterDeleteBench shows that agents with external memory can sometimes reconstruct a deleted target from related records.
- Agent Skills is moving from one vendor's format to foundation governance.: Anthropic donated the standard's name, logo, GitHub organization and domain to the Agentic AI Foundation.
- Investors are pricing agent traffic as web infrastructure.: Blackwall raised $100 million at a $2.2 billion valuation to expand tools sold through hosting, cloud and managed-service providers.
- November 2–3: SANS AI/SI Cybersecurity Summit, Arlington and virtual.: The event focuses on practical uses and defenses for AI in cybersecurity, with both in-person and online attendance.
Curator's Corner
I think bug bounties are pricing the wrong scarce resource.
The standard transaction still centers the report. HackerOne's own guidance says programs award bounties through submitted reports, often when a finding is confirmed as valid or after it is resolved. Its calculator starts with the affected asset and the report's severity. The money is attached to the finding, not to the full path toward a running fix.
AI is changing that cost curve. PHP says it closed 106 reports that were invalid, duplicate or unreproducible while publishing 15 CVEs since July 1. It also says AI tools have made reports much cheaper to write. Yet every verdict still requires a person to reproduce the issue, judge the impact and write or review the patch.
The two critical PHP flaws show what the bounty does not buy by itself. Maintainers had to design a compatible fix, test multiple supported branches, prepare source backports for older versions, coordinate mitigations with providers and help the ecosystem deploy. Discovery produced the input. Repair consumed the scarce capacity.