CVE-2026-65062 EGOR CVE debrief

Who should care

Users of Data::SortedSet::Shared versions before 0.03 for Perl should be aware of this vulnerability. Local users may be able to exploit this issue to access sensitive information. Affected operators, platforms, vulnerability-management, and security teams should review this vulnerability and plan accordingly.

Technical summary

The Data::SortedSet::Shared package creates a shared segment in a directory like /tmp or /dev/shm with a world-readable file mode of 0644. The open operation follows symlinks and silently uses a pre-existing file if it exists, rather than failing. This allows local attackers to plant a symlink or file to exploit the vulnerability. Defenders should review compensating controls for exposed systems while remediation is scheduled and verified.

Defensive priority

High

Recommended defensive actions

• Update to version 0.03 or later of Data::SortedSet::Shared
• Use compensating controls such as access controls and monitoring to limit access to shared segments
• Verify that local users do not have the ability to plant symlinks or files in shared directories
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record was published on 2026-07-21T20:17:05.190Z and last modified on 2026-07-22T16:21:53.517Z. The NVD entry is currently Deferred. Evidence is limited to CVE and NVD information. Defenders should verify affected product deployments, review official advisories, and plan updates or mitigations. Monitoring and compensating controls are recommended while remediation is scheduled.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.