Critical Vulnerability in Unbound Package: CVE-2026-42534

unbound Updated 22 Oct 2026

Summary

20/05/2026
N/A
No i
Unrated
Not published

DEBIAN-CVE-2026-42534: ... Affects unbound versions 1.13.1-1 – 1.25.0-1. 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

Unbound is a validating, recursive, and caching DNS resolver that is widely used for its performance and security features. It is designed to provide secure DNS resolution and prevent various types of DNS attacks. However, recent findings have identified a vulnerability (CVE-2026-42534) that affects multiple Debian distributions, potentially compromising the integrity and security of DNS queries.

Vulnerability Detail

CVE-2026-42534 is a critical vulnerability that originates from a flaw in the Unbound DNS resolver. This vulnerability allows attackers to exploit the DNS resolution process, potentially leading to unauthorized access to sensitive data or manipulation of DNS responses. The implications of this vulnerability are severe, as it can facilitate various attacks, including DNS spoofing and cache poisoning, which could compromise the security of users relying on the affected DNS resolver.

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 consider disabling certain features of Unbound that may be exploited until a patch is applied. However, it is strongly recommended to update to the patched version as soon as it becomes available to ensure full protection.

Conclusion

CVE-2026-42534 poses a significant risk to systems using the Unbound DNS resolver across multiple Debian distributions. It is crucial for users to update their Unbound packages to the latest versions to protect against potential exploits. Regular monitoring of vulnerabilities using tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for unbound →

Share this vulnerability

FAQ

CVE-2026-42534 is a critical vulnerability found in the Unbound DNS resolver that could allow attackers to manipulate DNS queries.

If exploited, this vulnerability could lead to unauthorized access to sensitive data and compromise the integrity of DNS responses.

The vulnerability affects Unbound across multiple Debian distributions, including versions 11 (bullseye), 12 (bookworm), 13 (trixie), and 14 (forky).

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

If an immediate update is not possible, consider disabling certain features of Unbound that may be exploited until a patch is applied.

Related vulnerabilities

Recent vulnerabilities recorded for unbound.

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