Vulnerabilities

Vulnerability · USN-8925-1

libyaml-perl vulnerabilities

Published Oct 14, 2026 · catalog updated Oct 14, 2026 · libyaml-perl vulnerabilities

Open the advisory

Exploitation likelihood is not on this record for USN-8925-1. A missing EPSS score is not a low risk. Compare libyaml-perl vulnerabilities with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (libyaml-perl vulnerabilities).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Advisory link
Affected products
Ubuntu:22.04:LTS libyaml-perl · Ubuntu:24.04:LTS libyaml-perl · Ubuntu:Pro:16.04:LTS libyaml-perl · Ubuntu:Pro:18.04:LTS libyaml-perl · Ubuntu:Pro:20.04:LTS libyaml-perl · Ubuntu:Pro:26.04:LTS libyaml-perl

Dominique Dumont discovered that YAML-LibYAML did not correctly handle certain reflection operations. If a user or system were tricked into opening a specially crafted file, an attacker could possibly use this issue to delete files. This issue only affected Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. (CVE-2017-20285) It was discovered that YAML-LibYAML did not correctly handle parsing certain documents. If a user or automated system were tricked into opening a specially crafted file, an attacker could possibly use this issue to execute arbitrary code. This issue only affected Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. (CVE-2019-25777) It was discovered that YAML-LibYAML contained a regular expression susceptible to catastrophic backtracking. If a user or automated system were tricked into opening a specially crafted file, an attacker could possibly use this issue to cause a denial of service. (CVE-2026-63676)

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • Ubuntu:22.04:LTS libyaml-perl0 → 1.30-1ubuntu0.22.04.1
  • Ubuntu:24.04:LTS libyaml-perl0 → 1.31-1ubuntu0.24.04.1
  • Ubuntu:Pro:16.04:LTS libyaml-perl0 → 1.15-1ubuntu0.1~esm1
  • Ubuntu:Pro:18.04:LTS libyaml-perl0 → 1.24-1ubuntu0.1~esm1
  • Ubuntu:Pro:20.04:LTS libyaml-perl0 → 1.30-1ubuntu0.20.04.1~esm1
  • Ubuntu:Pro:26.04:LTS libyaml-perl0 → 1.31-1ubuntu0.26.04.1~esm1

How to fix USN-8925-1

  • Recommended remediation

    A patch or advisory reference is linked. Open the original publisher for availability by product version.

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for USN-8925-1. A missing EPSS score is not a low risk. Compare libyaml-perl vulnerabilities with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with 0 → 1.30-1ubuntu0.22.04.1, 0 → 1.31-1ubuntu0.24.04.1, 0 → 1.15-1ubuntu0.1~esm1, 0 → 1.24-1ubuntu0.1~esm1, 0 → 1.30-1ubuntu0.20.04.1~esm1, 0 → 1.31-1ubuntu0.26.04.1~esm1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Detected

    Dominique Dumont discovered that YAML-LibYAML did not correctly handle certain reflection operations. If a user or system were tricked into opening a specially crafted file, an attacker could possibly use this issue to delete files. This issue only affected Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. (CVE-2017-20285) It was discovered that YAML-LibYAML did not correctly handle parsing certain documents

  2. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    libyaml-perl fixed in 1.15-1ubuntu0.1~esm1; libyaml-perl fixed in 1.24-1ubuntu0.1~esm1; libyaml-perl fixed in 1.30-1ubuntu0.20.04.1~esm1; libyaml-perl fixed in 1.30-1ubuntu0.22.04.1

  3. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    libyaml-perl fixed in 1.15-1ubuntu0.1~esm1

  4. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    libyaml-perl fixed in 1.24-1ubuntu0.1~esm1

  5. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    libyaml-perl fixed in 1.30-1ubuntu0.20.04.1~esm1

  6. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    libyaml-perl fixed in 1.30-1ubuntu0.22.04.1

  7. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    libyaml-perl fixed in 1.31-1ubuntu0.24.04.1

  8. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Fix available

    libyaml-perl fixed in 1.31-1ubuntu0.26.04.1~esm1

  9. Oct 14, 2026 · OpenSSF OSV / OSV Scanner

    Updated

    Dominique Dumont discovered that YAML-LibYAML did not correctly handle certain reflection operations. If a user or system were tricked into opening a specially crafted file, an attacker could possibly use this issue to delete files. This issue only affected Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. (CVE-2017-20285) It was discovered that YAML-LibYAML did not correctly handle parsing certain documents

Sources

References

Freshness

Last verified in this catalog Oct 14, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.