Critical Vulnerability in Zaqar Package: CVE-2026-66139 Exposes Security Risks

zaqar Updated 22 Oct 2026

Summary

24/07/2026
N/A
No i
Medium
4.8

DEBIAN-CVE-2026-66139: ... Affects zaqar versions 15.0.0-1 – 22.0.0~rc1-2. 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

Zaqar is an open-source messaging service designed for cloud applications, providing a reliable way to manage messages between different components. It supports multiple messaging patterns and is often used in distributed systems. However, recent findings have revealed a vulnerability (CVE-2026-66139) that could potentially expose sensitive data, making it crucial for users to understand and address this issue promptly.

Vulnerability Detail

The vulnerability identified as CVE-2026-66139 affects the Zaqar package across multiple Debian distributions. It originates from improper handling of certain input parameters, which could allow an attacker to exploit the system, leading to potential data leakage. The vulnerability has a CVSS score of 4.8, indicating a moderate severity level. If left unaddressed, it could result in unauthorized access to sensitive information, impacting the integrity and confidentiality of the messaging service.

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

As a temporary workaround, users can restrict access to the Zaqar service by implementing firewall rules or adjusting permissions to limit exposure until the package is updated. For example, you can use the following command to block access to the service:

sudo ufw deny <port_number>

Replace <port_number> with the actual port used by Zaqar.

Conclusion

The CVE-2026-66139 vulnerability in the Zaqar package poses a significant risk to users, potentially leading to unauthorized access to sensitive information. It is essential to update the package to the latest version to mitigate this risk. Users are encouraged to utilize available tools like Vulert to monitor their applications for vulnerabilities effectively.

See every vulnerability recorded for zaqar →

Share this vulnerability

FAQ

CVE-2026-66139 is a vulnerability found in the Zaqar messaging service that could allow unauthorized access to sensitive data.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

If you cannot update the package immediately, consider implementing firewall rules or adjusting permissions to limit access to the Zaqar service as a temporary workaround.

The vulnerability has a CVSS score of 4.8, indicating a moderate severity level.

You can visit Vulert at https://vulert.com, which monitors and alerts for open-source vulnerabilities in your software using just a manifest file.

Related vulnerabilities

Recent vulnerabilities recorded for zaqar.

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