alsa-2025:9330
Vulnerability from osv_almalinux
Published
2025-06-23 00:00
Modified
2025-07-03 08:23
Summary
Important: perl-YAML-LibYAML security update
Details
Kirill Siminov's "libyaml" is arguably the best YAML implementation. The C library is written precisely to the YAML 1.1 specification. It was originally bound to Python and was later bound to Ruby.
Security Fix(es):
- yaml-libyaml: LibYAML Perl File Modification Vulnerability (CVE-2025-40908)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
{
"affected": [
{
"package": {
"ecosystem": "AlmaLinux:9",
"name": "perl-YAML-LibYAML"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1:0.82-6.1.el9_6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"details": "Kirill Siminov\u0027s \"libyaml\" is arguably the best YAML implementation. The C library is written precisely to the YAML 1.1 specification. It was originally bound to Python and was later bound to Ruby. \n\nSecurity Fix(es): \n\n * yaml-libyaml: LibYAML Perl File Modification Vulnerability (CVE-2025-40908)\n\n\nFor more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.\n",
"id": "ALSA-2025:9330",
"modified": "2025-07-03T08:23:21Z",
"published": "2025-06-23T00:00:00Z",
"references": [
{
"type": "ADVISORY",
"url": "https://access.redhat.com/errata/RHSA-2025:9330"
},
{
"type": "REPORT",
"url": "https://access.redhat.com/security/cve/CVE-2025-40908"
},
{
"type": "REPORT",
"url": "https://bugzilla.redhat.com/2369630"
},
{
"type": "ADVISORY",
"url": "https://errata.almalinux.org/9/ALSA-2025-9330.html"
}
],
"related": [
"CVE-2025-40908"
],
"summary": "Important: perl-YAML-LibYAML security update"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…