# CVE-2026-33611: PowerDNS Authoritative Server database corruption via REST API

Source: https://junglewise.ai/threats/cve-2026-33611-powerdns-authoritative-server-database-corruption-via-rest-api  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-04-22. Updated: 2026-05-14  
License: CC BY 4.0 with a link back

CVE-2026-33611 · Severity: medium · CVSS 6.5 · Published 2026-04-22

PowerDNS Authoritative Server is a widely used system for managing domain name records. A vulnerability exists where an authorized administrator using the management interface can input specific types of malformed data. This can lead to the corruption of the underlying database, potentially causing service outages or loss of DNS record integrity.

Technologies: [Powerdns Authoritative Server](https://junglewise.ai/threats/technologies/authoritative-server). Vendors: [Powerdns](https://junglewise.ai/threats/vendors/powerdns).

## Quick answers

**Is CVE-2026-33611 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-33611 being exploited in the wild.

**How severe is CVE-2026-33611?** Medium severity, with a CVSS score of 6.5, published 22 April 2026.

**Which products and versions are affected?** Powerdns Authoritative Server 4.9.0 to 4.9.13, 5.0.0 to 5.0.3.

**Is there a fix for CVE-2026-33611?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-33611 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-33611?** Check whether you run Powerdns Authoritative Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is classified as an integer overflow (CWE-190) occurring during the processing of HTTPS or SVCB records via the REST API. When the LMDB storage backend is in use, the injection of specifically crafted invalid record data triggers a corruption of the database. This requires high privileges (operator access to the REST API) but can result in a complete loss of integrity and availability for the affected database. The issue is addressed in PowerDNS Authoritative versions 4.9.14 and 5.0.4.

## Affected products

- PowerDNS Authoritative Server 4.9.0 to 4.9.13, 5.0.0 to 5.0.3

## Timeline

- 2026-04-22: disclosed
- 2026-04-22: advisory

## References

- [https://docs.powerdns.com/authoritative/security-advisories/powerdns-advisory-powerdns-2026-05.html](https://docs.powerdns.com/authoritative/security-advisories/powerdns-advisory-powerdns-2026-05.html)

## Related threats

- [PowerDNS Authoritative Server denial of service in internal web server](https://junglewise.ai/threats/cve-2026-42005-powerdns-authoritative-server-denial-of-service-in-internal-web)
- [PowerDNS Authoritative Server denial of service in catalog zone transfer](https://junglewise.ai/threats/cve-2026-42396-powerdns-authoritative-server-denial-of-service-in-catalog-zone)
- [PowerDNS Authoritative Server denial of service in GSS-TSIG](https://junglewise.ai/threats/cve-2026-42002-powerdns-authoritative-server-denial-of-service-in-gss-tsig)
- [PowerDNS Authoritative Server insufficient validation of Autoprimary SOA queries](https://junglewise.ai/threats/cve-2026-42001-powerdns-authoritative-server-insufficient-validation-of)
- [PowerDNS Authoritative Server insufficient name validation in AXFR](https://junglewise.ai/threats/cve-2026-42000-powerdns-authoritative-server-insufficient-name-validation-in)