CVE-2026-57076

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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 heap use-after-free via an anchor name reused as an anchors-table key in syck_hdlr_add_anchor.

In the bundled libsyck an anchor name allocated by syck_strndup is stored both as node->anchor, freed when the node is freed, and as the key in the parser's anchors table. Freeing the node frees the shared key, and a later anchor redefinition makes st_delete compare against the freed key, so st_strcmp reads freed heap memory. Anchors are a standard YAML feature and need no special flags, so this is reached on the default Load path.

Any caller that runs Load or LoadFile on an untrusted document that redefines an anchor reaches the read of freed memory.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/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
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
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-57076(1)

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

Affected Packages

(5 across 5 ecosystems)
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
perl-yaml-syck1.47-r0
Debian:11(1)
PackageVulnerable rangeFixed inDependents
libyaml-syck-perl1.34-1 ... 1.47-1 (9 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
libyaml-syck-perl1.34-2, 1.34-2+deb12u1, 1.34-2+deb12u21.34-2+deb12u3
Debian:13(1)
PackageVulnerable rangeFixed inDependents
libyaml-syck-perl1.34-2, 1.34-2+deb13u1, 1.34-2+deb13u21.34-2+deb13u3
Debian:14(1)
PackageVulnerable rangeFixed inDependents
libyaml-syck-perl1.34-2 ... 1.36-3 (6 versions)1.47-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 77× 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 610 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-57076?
CVE-2026-57076 is a high vulnerability published on July 16, 2026. YAML::Syck versions before 1.47 for Perl allow a heap use-after-free via an anchor name reused as an anchors-table key in syckhdlradd_anchor. In the bundled libsyck an anchor name allocated by syckstrndup is stored both as node->anchor, freed when the node is freed, and as the key in the parser's…
When was CVE-2026-57076 disclosed?
CVE-2026-57076 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-57076 actively exploited?
CVE-2026-57076 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-57076?
CVE-2026-57076 has a CVSS v3.1 base score of 7.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-57076?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57076, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-57076

Explore →

Is Your Infrastructure Affected by CVE-2026-57076?

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