TINITA YAML-LibYAML up to 0.902.x on Perl YAML::LibYAML file access
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in TINITA YAML-LibYAML up to 0.902.x on Perl and classified as problematic. This issue affects the function YAML::LibYAML. The manipulation results in file access.
This vulnerability is identified as CVE-2025-40908. There is not any exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in TINITA YAML-LibYAML up to 0.902.x on Perl. It has been classified as problematic. Affected is the function YAML::LibYAML. The manipulation with an unknown input leads to a file access vulnerability. CWE is classifying the issue as CWE-552. The product makes files or directories accessible to unauthorized actors, even though they should not be. This is going to have an impact on confidentiality. CVE summarizes:
YAML-LibYAML prior to 0.903.0 for Perl uses 2-args open, allowing existing files to be modified
The weakness was released by @shlomif as 120. The advisory is shared for download at github.com. This vulnerability is traded as CVE-2025-40908 since 04/16/2025. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1083.
The vulnerability scanner Nessus provides a plugin with the ID 240265 (RHEL 8 : perl-YAML-LibYAML (RHSA-2025:9329)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 0.903.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at Tenable (240265). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: File accessCWE: CWE-552 / CWE-425
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 240265
Nessus Name: RHEL 8 : perl-YAML-LibYAML (RHSA-2025:9329)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: YAML-LibYAML 0.903.0
Patch: github.com
Timeline
04/16/2025 🔍06/01/2025 🔍
06/01/2025 🔍
06/23/2025 🔍
Sources
Advisory: 120Researcher: @shlomif
Status: Confirmed
CVE: CVE-2025-40908 (🔍)
GCVE (CVE): GCVE-0-2025-40908
GCVE (VulDB): GCVE-100-310776
Entry
Created: 06/01/2025 18:35Updated: 06/23/2025 20:34
Changes: 06/01/2025 18:35 (59), 06/03/2025 05:15 (1), 06/23/2025 20:34 (2)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.