Can this vulnerability be exploited remotely?

Yes, in many deployments. If sandbox identifiers or configuration parameters are derived from or influenced by user-controlled input, a remote attacker may be able to craft values that collide under SHA-1 and thereby poison the cache.

What level of access does an attacker need?

The attacker needs the ability to influence or control the data that is hashed into the sandbox identifier cache key. This might be direct (e.g., specifying an identifier or configuration) or indirect (e.g., controlling fields that the system incorporates into the hash).

What is the safest general fix pattern?

The safest approach is to replace SHA-1 with a modern, collision-resistant hash function and ensure that cache keys used for sandbox identification do not rely solely on hash uniqueness for security. Keys should be derived from robust, well-scoped identifiers, preferably bound to tenant and context.

Severity:

HIGH RISK

(7.5)

Use of Weak Cryptographic Hash (CWE-327) in OpenClaw Sandbox Configuration Caching

CVE-2026-28479

Published:

Mar 5, 2026

Status:

Received

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-78

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

Remote Code Execution

March 7, 2026

CWE-89

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Remote Code Execution via SQL Injection on the Database Server

March 7, 2026

Vulnerability Type

Category:

Use of Weak Cryptography

CWE:

CWE-327

Impact:

Sandbox Escape via Cache Poisoning / Configuration Confusion

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

Use of Weak Cryptography

CWE:

CWE-327

Impact:

Sandbox Escape via Cache Poisoning / Configuration Confusion

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Use of Weak Cryptographic Hash (CWE-327) in OpenClaw Sandbox Configuration Caching

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

CRITICAL RISK

CRITICAL

(9.9)

Command Injection in MCP Stdio Configuration Validation (CWE-78) in WeKnora

CRITICAL RISK

CRITICAL

(9.9)

SQL Injection via PostgreSQL Array/Row Expressions (CWE-89) in WeKnora Query Engine

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare