Last week we announced Echo's partnership with Nano Claw, designed to extend the vision and security of the open source project. We scan the upstream Nano Claw container using Trivy, Grype, and Wiz. Raw results show vulnerabilities sorted by severity.

First, we separate findings into 'safe to bump' and 'needs real work.' Libraries like Chromium are safe to upgrade. After stripping Chromium-related CVEs, we're left with roughly 600 vulnerabilities needing fixing. Some upgrades require major version jumps, so we patch and verify. For instance, Hono's node-server flagged a major jump, but the fix was available closer to the installed version; we added it to the advisory.

Next, for 'won't fix' findings, we backport patches from newer versions. In one case, CVE-2025-59375 in expat involved a security fix that wasn't a simple bounds check. An attacker could send a ~250 KiB XML document causing ~800 MiB allocation—an amplification factor of about 3,300. The fix required introducing allocation accounting across 9 files. We treated it as a rebase rather than an apply, running end-to-end: apply, build, test, diagnose failures, and repeat until all tests pass.

On top of application dependencies, Nano Claw's Dockerfile builds on Debian 12, bringing OS-level vulnerabilities. Echo OS eliminates more than 1.1 million CVEs across thousands of patched OS packages, built from source and continuously patched by AI agents.