Four perfect 10s and a 9.9 sandbox escape: Spinnaker, Perl, and OpenClaw all need attention

Perl's Storable module before version 3.05 has a stack overflow triggered by a signed/unsigned mismatch when reading class name lengths. An attacker who can feed crafted serialized data to your Perl process can crash it or potentially run arbitrary code. Exploitation requires the app to deserialize untrusted Storable blobs, so if you only deserialize data you control, your exposure is lower.

Included because

prioritization factors: exploitation, exposure, prevalence, patch quality, and blast radius

Affected estate

Anyone running Perl applications that use Storable (before 3.05) to deserialize data from untrusted sources

How to check

Check inventory, endpoint management, or the vendor console for affected product versions.

Action

Upgrade the Storable module to 3.05 or later, and audit code paths to confirm you aren't thawing untrusted input.

Urgency

Patch this week

Why it matters

Perl's Storable module before version 3

Source

NVD

Spinnaker's expression parsing in the Echo pipeline triggers component doesn't restrict context handling, which lets an attacker inject expressions that execute arbitrary code on the server. No authentication bypass is needed if the attacker can submit or modify a pipeline definition. CVSS 10.0, not yet exploited in the wild, and EPSS is low (0.00057), but the impact is full remote code execution.

Included because

prioritization factors: exploitation, exposure, prevalence, patch quality, and blast radius

Affected estate

Teams running Spinnaker with the echo-pipelinetriggers component

How to check

Check inventory, endpoint management, or the vendor console for affected Spinnaker versions.

Action

Update the echo-pipelinetriggers artifact to the patched version and restrict who can create or edit pipeline definitions until the update is live.

Urgency

Patch within 24 hours

Why it matters

Spinnaker's expression parsing in the Echo pipeline triggers component doesn't restrict context handling, which lets an attacker inject expressions that execute arbitrary code on the server

Source

GitHub

If you use Spinnaker's gitrepo artifact type, an attacker can inject commands through the branch name or file path fields. The clouddriver-artifacts-gitrepo module doesn't properly sanitize user input, so a crafted pipeline config gives the attacker remote code execution on the Clouddriver host. CVSS 10.0, not yet exploited in the wild.

Included because

prioritization factors: exploitation, exposure, prevalence, patch quality, and blast radius

Affected estate

Teams running Spinnaker with gitrepo artifact types enabled (clouddriver-artifacts-gitrepo)

How to check

Check inventory, endpoint management, or the vendor console for affected Spinnaker versions.

Action

Update clouddriver-artifacts-gitrepo to the patched release, and as a stopgap, disable or restrict gitrepo artifact definitions until the fix is deployed.

Urgency

Patch within 24 hours

Why it matters

If you use Spinnaker's gitrepo artifact type, an attacker can inject commands through the branch name or file path fields

Source

GitHub

OpenClaw before 2026.3.31 has a sandbox escape. An attacker can manipulate the senderIsOwner parameter and abuse heartbeat context inheritance to bypass sandbox restrictions and escalate privileges. The attack doesn't require physical access, but the attacker does need some level of existing access within the sandboxed environment to trigger it.

Included because

prioritization factors: exploitation, exposure, prevalence, patch quality, and blast radius

Affected estate

Anyone running OpenClaw versions older than 2026.3.31

How to check

Check inventory, endpoint management, or the vendor console for affected product versions.

Action

Upgrade OpenClaw to version 2026.3.31 or later and review any sandbox-hosted workloads for signs of unexpected privilege escalation.

Urgency

Patch within 24 hours

Why it matters

OpenClaw before 2026

Source

NVD