CVE-2026-63676

unknown
Published 2026-10-14 · Modified —
CVSS v3
—
CVSS v4 NEW
—
not yet in upstream
VIR risk
—

Description

YAML-LibYAML vulnerabilities

Predictions

Exploit likelihood
20%
Patch ETA
—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

Propose a mitigation on Community Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

debian Debian Mixed 5 releases
VersionPackageStatusFixed in
trixie libyaml-perl Affected —
sid libyaml-perl Fixed 1.321-1
forky libyaml-perl Fixed 1.321-1
bullseye libyaml-perl Affected —
bookworm libyaml-perl Affected —
alpine Alpine Fixed 1 release
VersionPackageStatusFixed in
v3.24 perl-yaml Fixed 1.320.0-r0
ubuntu Ubuntu Fixed 6 releases
VersionPackageStatusFixed in
xenial libyaml-perl Fixed 1.15-1ubuntu0.1~esm1
resolute libyaml-perl Fixed 1.31-1ubuntu0.26.04.1~esm1
noble libyaml-perl Fixed 1.31-1ubuntu0.24.04.1
jammy libyaml-perl Fixed 1.30-1ubuntu0.22.04.1
focal libyaml-perl Fixed 1.30-1ubuntu0.20.04.1~esm1
bionic libyaml-perl Fixed 1.24-1ubuntu0.1~esm1

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.