SUSE · pdns-recursor-5.4.8-1.1 on GA media
Affects SUSESource GCVE Database
Not known to be exploited · CVSS 8.2 High · fixed in SUSE package updates : patch SUSE pdns-recursor soon.
Data as of 12 Nov 2026, 13:47 UTC
- Patch
- Available – fixed in 5.3.1, 5.2.6, 5.1.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 12 Nov 2026.
What to do
Upgrade Recursor and pdns-recursor to 5.3.1, 5.2.6 or 5.1.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PowerDNSRecursor | Affected
| Fixed in
|
| PowerDNSRecursor | Affected
| Fixed in
|
| PowerDNSRecursor | Affected
| Fixed in
|
GitHubpdns-recursorpkg:github/pdns-recursorOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to pdns-recursor version 5.4.8-1.1 on openSUSE Tumbleweed to apply the security fixes. No additional mitigation guidance is provided.
Description
Multiple security issues affecting the pdns-recursor package were fixed in version 5.4.8-1.1 on the GA media of openSUSE Tumbleweed. The vulnerabilities are collectively addressed by this package update. No specific details about the nature of the vulnerabilities or their impact are provided.
References
- suse.com/support/security/rating/ (opens in a new tab)
- ftp.suse.com/pub/projects/security/csaf/2026/opensuse-su-2026_12532-1.json (opens in a new tab)
- suse.com/security/cve/CVE-2025-59023/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-59024/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-59029/ (opens in a new tab)
- suse.com/security/cve/CVE-2025-59030/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-0398/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-24027/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33256/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33257/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33258/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33259/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33260/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33261/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33262/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33600/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33601/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-33612/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-40012/ (opens in a new tab)
- suse.com/security/cve/CVE-2026-42005/ (opens in a new tab)