CVE-2026-64613

MEDIUMPre-NVD 6.26.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.2 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Trending — 5 sources updated this week
6.2
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Data::Buffer::Shared versions before 0.05 for Perl create a world-readable mmap backing file and open it without O_NOFOLLOW.

The segment is created in buf_generic.h with open(path, O_RDWR|O_CREAT|O_EXCL, 0666). O_EXCL blocks a pre-seeded file on create, but the mode is 0666, so under the default umask 022 the file is created mode 0644 (world-readable), and O_NOFOLLOW is absent, so a symlink planted at the path is followed when the segment is attached.

A "Shared" segment naturally lives in a shared directory such as /tmp or /dev/shm, where any local user can read the IPC payloads stored in the world-readable segment, and a pre-planted symlink at the path redirects the open to another file.

CVSS v3
6.2
EG Score
6.2(medium)
EG Risk
28(Track)
EG Risk 28/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity62% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
6.0%
KEV
Not listed

Published

July 21, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jul 23, 2026
No patch confirmed yet.
generic

Client Challenge

https://metacpan.org/release/EGOR/Data-Buffer-Shared-0.05/diff/EGOR/Data-Buffer-Shared-0.04#buf_generic.h
generic

Client Challenge

https://metacpan.org/release/EGOR/Data-Buffer-Shared-0.05/changes

Vendor Advisories for CVE-2026-64613(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 14× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 12:55 UTCEG score recompute▲ 6.20
  4. 2026-07-23 12:55 UTCGHSA enrichment
  5. 2026-07-23 12:54 UTCMITRE cvelistV5CVSS v3 → 6.2 · severity → MEDIUM
  6. 2026-07-23 03:22 UTCEG score recompute
  7. 2026-07-22 23:02 UTCEG score recompute
  8. 2026-07-22 23:01 UTCGHSA enrichment
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-22 14:08 UTCEPSS rescore
  11. 2026-07-21 21:34 UTCGHSA enrichment
  12. 2026-07-21 21:19 UTCNVD update
  13. 2026-07-21 19:44 UTCEG score recompute
  14. 2026-07-21 19:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-64613?
CVE-2026-64613 is a medium vulnerability published on July 21, 2026. Data::Buffer::Shared versions before 0.05 for Perl create a world-readable mmap backing file and open it without O_NOFOLLOW. The segment is created in bufgeneric.h with open(path, ORDWR|OCREAT|OEXCL, 0666). OEXCL blocks a pre-seeded file on create, but the mode is 0666, so under the default umask…
When was CVE-2026-64613 disclosed?
CVE-2026-64613 was first published in the National Vulnerability Database on July 21, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64613 actively exploited?
CVE-2026-64613 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-64613?
CVE-2026-64613 has a CVSS v3.1 base score of 6.2 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-64613?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64613, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-64613

Explore →

Is Your Infrastructure Affected by CVE-2026-64613?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs