CVE-2026-4851: Casiano Grid::machine remote code execution (CVSS 9.8)

Description

GRID::Machine versions through 0.127 for Perl allows arbitrary code execution via unsafe deserialization. GRID::Machine provides Remote Procedure Calls (RPC) over SSH for Perl. The client connects to remote hosts to execute code on them. A compromised or malicious remote host can execute arbitrary code back on the client through unsafe deserialization in the RPC protocol. read_operation() in lib/GRID/Machine/Message.pm deserialises values from the remote side using eval() $arg .= '$VAR1'; my $val = eval "no strict; $arg"; # line 40-41 $arg is raw bytes from the protocol pipe. A compromised remote host can embed arbitrary perl in the Dumper-formatted response: $VAR1 = do { system("..."); }; This executes on the client silently on every RPC call, as the return values remain correct. This functionality is by design but the trust requirement for the remote host is not documented in the distribution.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Casiano Grid::machine≤ 0.127

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://www.openwall.com/lists/oss-security/2026/03/26/6Mailing List
http://www.openwall.com/lists/oss-security/2026/03/26/6Mailing List

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-4851 being actively exploited?

CVE-2026-4851 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.78%.

How severe is CVE-2026-4851?

CVE-2026-4851 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.78% probability of exploitation.

Which products are affected by CVE-2026-4851?

Affected products include Casiano Grid::machine.

How do I fix CVE-2026-4851?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-4851 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo