Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-33611: An operator allowed to use the REST API can cause the Authoritative server to produce invalid HTTPS or SVCB re

32
Routine
MEDIUM 6.5UPGRADE

CVE-2026-33611 is a medium-severity flaw (CVSS 6.5) affecting authoritative. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An operator allowed to use the REST API can cause the Authoritative server to produce invalid HTTPS or SVCB record data, which can in turn cause LMDB database corruption, if using the LMDB backend.

Why this priority

  • No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score6.5 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededHigh
User interactionNone
EPSS exploit chance0.4% (top 64%)
CISA exploited listNo
WeaknessCWE-190
Published2026-04-22
Last modified2026-10-26
Publisher (CNA): Open-Xchange · Vendor: powerdns

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

powerdns authoritative UPGRADE
Affected: >= 4.9.0 and < 4.9.14 · >= 5.0.0 and < 5.0.4
Fixed in: 4.9.14, 5.0.4
Safe to downgrade to: a release before 4.9.0
1. Check installed version
apt-cache policy authoritative || rpm -q authoritative || authoritative --version
2. UPGRADE to 4.9.14 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade authoritative
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade authoritative
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 4.9.0 (Debian / Ubuntu)
apt-cache madison authoritative sudo apt install authoritative=<VERSION_BEFORE_4.9.0> sudo apt-mark hold authoritative
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list authoritative sudo dnf downgrade authoritative-<VERSION_BEFORE_4.9.0> sudo dnf versionlock add authoritative
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33611?

authoritative: upgrade to 4.9.14, 5.0.4. Exact commands for each OS are on this page.

Is CVE-2026-33611 being exploited?

CVE-2026-33611 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33611 affect?

CVE-2026-33611 affects authoritative. Severity is medium (CVSS 6.5). An operator allowed to use the REST API can cause the Authoritative server to produce invalid HTTPS or SVCB record data, which can in turn cause LMDB database corruption, if using the LMDB backend.

How urgent is CVE-2026-33611?

Priority 32/100. No elevated risk signals yet.

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.