CVE-2026-33611 json
Insufficient validation of HTTPS and SVCB records
published 2026-04-22 6 mo ago modified 2026-10-26 13 d ago also EUVD-2026-24951
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- PowerDNS Authoritative 4.9.14, 5.0.4
- pdns Debian 13 4.9.14-0+deb13u1
- pdns Debian 14 5.0.4-1
debian advisories DEBIAN-CVE-2026-33611
- pdns Alpine 3.24, Alpine 3.23 5.0.4-r0
alpine advisories ALPINE-CVE-2026-33611
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-33611 updated cvss 6.5
powerdns: LMDB: PowerDNS: Database corruption due to invalid record data
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H |
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H |
Affected products
- PowerDNS Authoritative
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
Sources
- CVE List CVE-2026-33611
- NVD CVE-2026-33611
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.