Is CVE-2026-64617 exploited in the wild?

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

How severe is CVE-2026-64617?

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

Which products and versions are affected?

Vividsnow Data::PubSub::Shared before 0.07.

Is there a fix for CVE-2026-64617?

A patch was published on 2026-07-03: Version 0.07 released with security hardening. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-64617 attacked?

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

Am I affected by CVE-2026-64617?

Check whether you run Vividsnow Data::PubSub::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-64617: Data::PubSub::Shared insecure file permissions and symlink following

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

A vulnerability in the Data::PubSub::Shared Perl module, which is used for high-performance communication between different processes on a computer, could allow local users to spy on or interfere with private data. Because the software creates temporary files with insecure permissions and fails to verify if those files have been tampered with, a malicious user on the same system could read sensitive message payloads or redirect the application to write data to unauthorized locations. This could lead to the exposure of internal application data or a disruption of service.

Vendors: Vividsnow.

Quick answers

Is CVE-2026-64617 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-64617 being exploited in the wild.
How severe is CVE-2026-64617?: Informational severity, with a CVSS score of 0, published 21 July 2026.
Which products and versions are affected?: Vividsnow Data::PubSub::Shared before 0.07.
Is there a fix for CVE-2026-64617?: A patch was published on 2026-07-03: Version 0.07 released with security hardening. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-64617 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-64617?: Check whether you run Vividsnow Data::PubSub::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

Data::PubSub::Shared versions prior to 0.07 utilize insecure file operations when creating mmap backing files in shared directories like /tmp or /dev/shm. Specifically, the module uses open() with mode 0666, which results in world-readable files (0644) under standard umask settings, exposing Inter-Process Communication (IPC) payloads to all local users. Furthermore, the absence of O_EXCL and O_NOFOLLOW flags in the open() call allows a local attacker to win a race condition by pre-planting a file or a symbolic link at the expected path, potentially leading to unauthorized data access or arbitrary file writes. The issue was addressed in version 0.07 by changing the default file mode to 0600 and hardening the file opening logic.

Affected products

EGOR (vividsnow) Data::PubSub::Shared before 0.07

Timeline

2026-07-03: patched: Version 0.07 released with security hardening.
2026-07-21: disclosed: CVE-2026-64617 published.

References

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