Is CVE-2026-64616 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-64616 being exploited in the wild.

How severe is CVE-2026-64616?

Informational severity, with a CVSS score of 0, published 21 July 2026.

Which products and versions are affected?

Vividsnow Data::NDArray::Shared < 0.02.

Is there a fix for CVE-2026-64616?

A patch was published on 2026-07-21: Fixed in version 0.02 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-64616 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-64616?

Check whether you run Vividsnow Data::NDArray::Shared at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-64616: Data::NDArray::Shared insecure file permissions and symlink following

Q: Is there a fix for CVE-2026-64616?

A patch was published on 2026-07-21: Fixed in version 0.02 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-64616 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-64616?

Check whether you run Vividsnow Data::NDArray::Shared at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-64616 · Severity: info · CVSS 0 · Published 2026-07-21

A vulnerability in the Data::NDArray::Shared Perl module, which is used for sharing large data arrays between processes, could allow local users to access sensitive information. The software creates temporary files with insecure permissions, meaning any user on the same system can read the data being processed. Additionally, a malicious user could trick the system into overwriting or using incorrect files, potentially leading to data corruption or unauthorized data access.

Vendors: Vividsnow.

Quick answers

Is CVE-2026-64616 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-64616 being exploited in the wild.
How severe is CVE-2026-64616?: Informational severity, with a CVSS score of 0, published 21 July 2026.
Which products and versions are affected?: Vividsnow Data::NDArray::Shared < 0.02.
Is there a fix for CVE-2026-64616?: A patch was published on 2026-07-21: Fixed in version 0.02 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-64616 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-64616?: Check whether you run Vividsnow Data::NDArray::Shared at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the ndarray.h component of Data::NDArray::Shared before version 0.02. The software uses open() with O_RDWR|O_CREAT and a mode of 0666 to create mmap backing files, which results in world-readable files (0644) under default umask settings. Furthermore, the absence of O_EXCL and O_NOFOLLOW flags allows a local attacker to perform a symlink attack or win a race condition to pre-plant a file in shared directories like /tmp or /dev/shm. This leads to local information disclosure of IPC payloads and potential redirection of file operations. The issue is addressed in version 0.02.

Affected products

EGOR (vividsnow) Data::NDArray::Shared < 0.02

Timeline

2026-07-21: disclosed
2026-07-21: advisory
2026-07-21: patched: Fixed in version 0.02

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.