Critical Vulnerability in Unbound Package: CVE-2026-33278

unbound Updated 22 Oct 2026

Summary

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

DEBIAN-CVE-2026-33278: ... 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Unbound is a validating, recursive, and caching DNS resolver designed to provide secure and efficient DNS services. It is widely used in various environments for its performance and security features. However, recent findings have identified a critical vulnerability (CVE-2026-33278) affecting multiple Debian distributions, which could potentially compromise the integrity and security of DNS queries.

Vulnerability Detail

CVE-2026-33278 is a vulnerability in the Unbound package that allows attackers to exploit weaknesses in DNS resolution processes. This vulnerability could lead to unauthorized access to sensitive information or manipulation of DNS responses, resulting in potential data breaches or service disruptions. The vulnerability is present in all versions of Unbound prior to the patch, making it critical for users to address this issue promptly.

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 disable certain features of Unbound that may be exploited until a patch is applied. This can be done by modifying the Unbound configuration file (usually located at /etc/unbound/unbound.conf) to limit the types of DNS queries processed. However, this is not a permanent solution and should only be used until the package is updated.

Conclusion

The CVE-2026-33278 vulnerability in the Unbound package poses significant risks to users relying on this DNS resolver. It is crucial to update to the latest patched version to ensure the security and integrity of DNS services. Users are encouraged to monitor their systems and apply necessary updates promptly.

See every vulnerability recorded for unbound →

Share this vulnerability

FAQ

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

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The risks include unauthorized access to sensitive data, manipulation of DNS queries, and potential service disruptions.

Yes, a patch is available. Users should update their Unbound package to the latest version to mitigate the risk.

If immediate updates are not possible, consider applying temporary workarounds, such as modifying the Unbound configuration to limit query types.

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