CVE-2026-13713

MEDIUMPre-NVD 6.26.2
EchelonGraph scoreHIGH confidence

Score 6.2 from GitHub Security Advisory published 2026-07-17. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 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.

YAML::Syck versions before 1.47 for Perl allow a use-after-free and double-free via an anchor node freed while still on the parser value stack.

In the bundled libsyck, when an anchor name is redefined or removed, syck_hdlr_add_anchor and syck_hdlr_remove_anchor free the node stored under that name with syck_free_node. That node can still be live on the parser's value stack, so syck_hdlr_add_node reaches it again and frees it a second time. On a normal build the 48-byte node chunk is freed twice and the interpreter aborts. Anchors need no special flags, so this is reached on the default Load path, and a 7-byte document that redefines an anchor triggers it.

Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor mid-parse crashes the interpreter, a denial of service.

CVSS v3
6.2
EG Score
6.2(high)
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
3.3%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 17, 2026

Advisory Details (2)

Auto-updated Jul 17, 2026
No patch confirmed yet.

Vendor Advisories for CVE-2026-13713(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 11× in last 7d / 431× 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.

Showing the most recent 100 of 431 total refreshes for this CVE.

  1. 2026-07-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:05 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:30 UTCEPSS rescore
  8. 2026-07-19 02:33 UTCEG score recompute
  9. 2026-07-19 02:33 UTCGHSA enrichment
  10. 2026-07-19 02:28 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-17 13:34 UTCEG score recompute 6.20
  13. 2026-07-17 13:34 UTCGHSA enrichment
  14. 2026-07-17 13:34 UTCMITRE cvelistV5CVSS v3 → 6.2 · severity → MEDIUM
  15. 2026-07-17 13:33 UTCGHSA enrichment
  16. 2026-07-17 13:32 UTCGHSA enrichment
  17. 2026-07-17 13:31 UTCGHSA enrichment
  18. 2026-07-17 13:30 UTCGHSA enrichment
  19. 2026-07-17 13:29 UTCGHSA enrichment
  20. 2026-07-17 13:29 UTCGHSA enrichment
  21. 2026-07-17 13:27 UTCGHSA enrichment
  22. 2026-07-17 13:25 UTCGHSA enrichment
  23. 2026-07-17 13:25 UTCGHSA enrichment
  24. 2026-07-17 13:23 UTCGHSA enrichment
  25. 2026-07-17 13:22 UTCGHSA enrichment
Show 75 more
  1. 2026-07-17 13:21 UTCGHSA enrichment
  2. 2026-07-17 13:20 UTCGHSA enrichment
  3. 2026-07-17 13:18 UTCGHSA enrichment
  4. 2026-07-17 13:17 UTCGHSA enrichment
  5. 2026-07-17 13:16 UTCGHSA enrichment
  6. 2026-07-17 13:15 UTCGHSA enrichment
  7. 2026-07-17 13:14 UTCGHSA enrichment
  8. 2026-07-17 13:13 UTCGHSA enrichment
  9. 2026-07-17 13:12 UTCGHSA enrichment
  10. 2026-07-17 13:10 UTCGHSA enrichment
  11. 2026-07-17 13:09 UTCGHSA enrichment
  12. 2026-07-17 13:08 UTCGHSA enrichment
  13. 2026-07-17 13:07 UTCGHSA enrichment
  14. 2026-07-17 13:06 UTCGHSA enrichment
  15. 2026-07-17 13:05 UTCGHSA enrichment
  16. 2026-07-17 13:04 UTCGHSA enrichment
  17. 2026-07-17 13:02 UTCGHSA enrichment
  18. 2026-07-17 12:59 UTCGHSA enrichment
  19. 2026-07-17 12:58 UTCGHSA enrichment
  20. 2026-07-17 12:56 UTCGHSA enrichment
  21. 2026-07-17 12:54 UTCGHSA enrichment
  22. 2026-07-17 12:53 UTCGHSA enrichment
  23. 2026-07-17 12:51 UTCGHSA enrichment
  24. 2026-07-17 12:49 UTCGHSA enrichment
  25. 2026-07-17 12:46 UTCGHSA enrichment
  26. 2026-07-17 12:44 UTCGHSA enrichment
  27. 2026-07-17 12:42 UTCGHSA enrichment
  28. 2026-07-17 12:41 UTCGHSA enrichment
  29. 2026-07-17 12:40 UTCGHSA enrichment
  30. 2026-07-17 12:39 UTCGHSA enrichment
  31. 2026-07-17 12:38 UTCGHSA enrichment
  32. 2026-07-17 12:34 UTCGHSA enrichment
  33. 2026-07-17 12:33 UTCGHSA enrichment
  34. 2026-07-17 12:33 UTCGHSA enrichment
  35. 2026-07-17 12:31 UTCGHSA enrichment
  36. 2026-07-17 12:28 UTCGHSA enrichment
  37. 2026-07-17 12:27 UTCGHSA enrichment
  38. 2026-07-17 12:26 UTCGHSA enrichment
  39. 2026-07-17 12:24 UTCGHSA enrichment
  40. 2026-07-17 12:23 UTCGHSA enrichment
  41. 2026-07-17 12:22 UTCGHSA enrichment
  42. 2026-07-17 12:22 UTCGHSA enrichment
  43. 2026-07-17 12:20 UTCGHSA enrichment
  44. 2026-07-17 12:19 UTCGHSA enrichment
  45. 2026-07-17 12:18 UTCGHSA enrichment
  46. 2026-07-17 12:16 UTCGHSA enrichment
  47. 2026-07-17 12:15 UTCGHSA enrichment
  48. 2026-07-17 12:14 UTCGHSA enrichment
  49. 2026-07-17 12:13 UTCGHSA enrichment
  50. 2026-07-17 12:12 UTCGHSA enrichment
  51. 2026-07-17 12:12 UTCGHSA enrichment
  52. 2026-07-17 12:10 UTCGHSA enrichment
  53. 2026-07-17 12:08 UTCGHSA enrichment
  54. 2026-07-17 12:07 UTCGHSA enrichment
  55. 2026-07-17 12:06 UTCGHSA enrichment
  56. 2026-07-17 12:05 UTCGHSA enrichment
  57. 2026-07-17 12:04 UTCGHSA enrichment
  58. 2026-07-17 12:04 UTCGHSA enrichment
  59. 2026-07-17 12:02 UTCGHSA enrichment
  60. 2026-07-17 11:58 UTCGHSA enrichment
  61. 2026-07-17 11:57 UTCGHSA enrichment
  62. 2026-07-17 11:56 UTCGHSA enrichment
  63. 2026-07-17 11:55 UTCGHSA enrichment
  64. 2026-07-17 11:54 UTCGHSA enrichment
  65. 2026-07-17 11:51 UTCGHSA enrichment
  66. 2026-07-17 11:51 UTCGHSA enrichment
  67. 2026-07-17 11:50 UTCGHSA enrichment
  68. 2026-07-17 11:49 UTCGHSA enrichment
  69. 2026-07-17 11:47 UTCGHSA enrichment
  70. 2026-07-17 11:44 UTCGHSA enrichment
  71. 2026-07-17 11:43 UTCGHSA enrichment
  72. 2026-07-17 11:41 UTCGHSA enrichment
  73. 2026-07-17 11:41 UTCGHSA enrichment
  74. 2026-07-17 11:39 UTCGHSA enrichment
  75. 2026-07-17 11:38 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-13713?
CVE-2026-13713 is a medium vulnerability published on July 16, 2026. YAML::Syck versions before 1.47 for Perl allow a use-after-free and double-free via an anchor node freed while still on the parser value stack. In the bundled libsyck, when an anchor name is redefined or removed, syckhdlraddanchor and syckhdlrremoveanchor free the node stored under that name with…
When was CVE-2026-13713 disclosed?
CVE-2026-13713 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13713 actively exploited?
CVE-2026-13713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-13713?
CVE-2026-13713 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-13713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13713, 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-13713

Explore →

Is Your Infrastructure Affected by CVE-2026-13713?

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