CVE-2026-13758

LOWPre-NVD 3.73.7—
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory (severity: LOW) published 2026-06-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 3.7; sources differ by 0.0.

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

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

CryptX versions before 0.088_001 for Perl compare AEAD authentication tags in non-constant time in the streaming decrypt_done path.

The decrypt_done($tag) form compares it against the computed tag with memNE (memcmp() != 0), which short-circuits on the first differing byte, so its run time depends on the number of matching leading bytes. This affects all five AEAD modes: GCM, CCM, ChaCha20Poly1305, EAX and OCB. The one-shot *_decrypt_verify helpers are unaffected; they verify the tag inside libtomcrypt with a constant-time comparison.

The timing difference is a tag-verification oracle. An attacker who can submit many candidate tags for the same nonce, ciphertext and associated data while measuring the timing precisely enough may recover the expected tag byte by byte and forge a message that verifies.

CVSS v3
3.7
EG Score
3.7(high)
EPSS
21.2%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 30, 2026

References (3)

Vendor Advisories for CVE-2026-13758(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 18× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 23:14 UTCEG score recompute
  4. 2026-07-05 23:14 UTCGHSA enrichment
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-02 22:05 UTCEG score recompute▲ 3.70
  9. 2026-07-02 22:05 UTCGHSA enrichment
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 14:32 UTCNVD updateCVSS v3 → 3.7 · severity → LOW
  14. 2026-06-30 00:21 UTCNVD update
  15. 2026-06-29 22:44 UTCMITRE cvelistV5
  16. 2026-06-29 21:26 UTCNVD update
  17. 2026-06-29 20:57 UTCEG score recompute
  18. 2026-06-29 20:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-13758?
CVE-2026-13758 is a low vulnerability published on June 29, 2026. CryptX versions before 0.088001 for Perl compare AEAD authentication tags in non-constant time in the streaming decryptdone path. The decryptdone($tag) form compares it against the computed tag with memNE (memcmp() != 0), which short-circuits on the first differing byte, so its run time depends on…
When was CVE-2026-13758 disclosed?
CVE-2026-13758 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13758 actively exploited?
CVE-2026-13758 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13758?
CVE-2026-13758 has a CVSS v3.1 base score of 3.7 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-13758?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13758, 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-13758

Explore →

Is Your Infrastructure Affected by CVE-2026-13758?

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

Start Free Scan →Browse All CVEs