Unmaintained Package Alert: zbus_names Crate Vulnerability

zbus_names Updated 17 Oct 2026

Summary

16/10/2026
N/A
No i
Unrated
Not published

RUSTSEC-2026-0371: zbus_names is unmaintained. Affects zbus_names 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

The zbus_names crate was designed to provide D-Bus name types for Rust applications, facilitating communication between different software components. However, it is no longer maintained as a standalone crate, having been merged into the zbus crate starting with version 6.0.0. This transition means that users relying on zbus_names must migrate to the updated zbus package to ensure continued support and functionality.

Vulnerability Detail

The vulnerability arises from the fact that the zbus_names crate is unmaintained, which means it will not receive updates, bug fixes, or security patches. This lack of maintenance can lead to potential security risks and compatibility issues for applications that continue to use it. Users may face challenges in integrating with newer versions of dependencies or addressing bugs that may arise in the future.

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 usage of zbus_names and monitoring for any issues that may arise. However, this is not a long-term solution, and migrating to zbus is strongly recommended.

Conclusion

The zbus_names crate is no longer maintained, presenting a vulnerability for users who continue to rely on it. Migrating to the zbus crate is essential for maintaining application security and functionality. Utilize tools like Vulert to monitor for vulnerabilities and ensure your software remains secure.

See every vulnerability recorded for zbus_names →

Share this vulnerability

FAQ

The zbus_names crate provided D-Bus name types for Rust applications, enabling communication between software components.

It is unmaintained, meaning it will not receive any updates or security patches, posing potential risks to applications using it.

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 usage of zbus_names and monitor for issues, but plan to migrate to the zbus crate as soon as possible.

Migrating to zbus ensures you have access to ongoing support, updates, and security patches, reducing the risk of vulnerabilities.

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