Unmaintained Package Alert: unsafe-libyaml Vulnerability

unsafe-libyaml Updated 12 Oct 2026

Summary

25/03/2024
N/A
No i
Unrated
Not published

RUSTSEC-2024-0449: unsafe-libyaml is unmaintained. Affects unsafe-libyaml versions >= 0.0.0-0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

unsafe-libyaml is a Rust library that serves as a machine translation of libyaml's C code into unsafe Rust using c2rust. It is primarily utilized for parsing YAML files and is a dependency for other libraries like serde_yaml, which is also deprecated. The library was archived by its owner on March 25, 2024, rendering it read-only and unmaintained, with the last release being version 0.2.11.

Vulnerability Detail

The vulnerability arises from the fact that unsafe-libyaml is no longer maintained, meaning that any bugs or security issues discovered in the library will not be addressed or patched. This poses a significant risk to applications relying on this library, as they may become vulnerable to exploits that could compromise data integrity or application stability. Additionally, since unsafe-libyaml is used by other libraries, the impact could cascade to those dependent projects.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

If immediate migration is not feasible, consider isolating the use of unsafe-libyaml and limiting its exposure within your application. However, this is not a long-term solution and should only be a temporary measure.

Conclusion

The unsafe-libyaml library is unmaintained, posing significant risks to applications that depend on it. It is crucial to transition to a maintained alternative to ensure the security and stability of your software. Utilize tools like Vulert to monitor for vulnerabilities in your projects.

See every vulnerability recorded for unsafe-libyaml →

Share this vulnerability

FAQ

unsafe-libyaml is a Rust library that translates libyaml's C code into unsafe Rust, primarily used for parsing YAML files.

It is unmaintained, meaning any bugs or security vulnerabilities will not be fixed, posing risks to applications that rely on it.

Consider using saphyr or noyalib, both of which are maintained and written in safe Rust.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Isolate the use of unsafe-libyaml in your application to limit exposure, but plan for a migration to a safer alternative as soon as possible.

Related vulnerabilities

Recent vulnerabilities recorded for unsafe-libyaml.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback