How to Fix CVE-2026-32977: OpenClaw (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-32977 is a sibling vulnerability in the same Openclaw OpenClaw advisory bundle as CVE-2026-32916. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-32977 matches the primary write-up.

What is different about CVE-2026-32977?

OpenClaw before 2026.3.11 contains a sandbox boundary bypass vulnerability in the fs-bridge writeFile commit step that uses an unanchored container path during the final move operation. An attacker can exploit a time-of-check-time-of-use race condition by modifying parent paths inside the sandbox to redirect committed files outside the validated writable path within the container mount namespace.

Impact is consistent with the bundle: exploitation of a race condition that can corrupt memory or state. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-32977

Apply the patched build per the primary write-up: How to Fix CVE-2026-32916.

For a quick check, confirm the running version of OpenClaw:

# Confirm the installed version via your package manager
dpkg -l | grep -i openclaw   # Debian/Ubuntu
rpm -qa | grep -i openclaw   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-32977 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-32977?

CVSS rates it 5.8 (Medium). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take OpenClaw offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-32977 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://github.com/openclaw/openclaw/security/advisories/GHSA-xvx8-77m6-gwg6
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-32977
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-32916

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Openclaw OpenClaw advisory bundle. Full procedure at how-to-fix-cve-2026-32916.*