agent-browser Flags Stale Chrome CVEs

This is a small but important security upgrade: browser automation tooling should treat browser freshness as part of runtime health, not an operator afterthought.

• –Makes vulnerable automation environments visible before agents browse sensitive sites
• –Helps teams catch stale custom Chrome installations that package updates cannot manage
• –CVE counts and upgrade guidance turn a vague warning into an actionable maintenance task
• –Particularly valuable for long-lived agents, CI workers, and serverless browser sessions
• –Reinforces that AI browser security depends on the browser engine, not just the agent sandbox