Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.5

How to Fix CVE-2026-33611: Authoritative (Bundle Sibling)

By Sai Kiran Pandrala

Last verified: 2026-05-25

CVE-2026-33611 is a sibling vulnerability in the same vendor advisory as CVE-2026-33608. Applying the patched build named in the primary write-up closes this CVE as well.

⚡ At a glance
SeverityCVSS 6.5 - Medium
Actively exploited?Not currently in CISA KEV
AffectedSame as the bundle - see CVE-2026-33608
Fixed inSame patched build as CVE-2026-33608 (See vendor advisory)
Type (CWE)Integer Overflow or Wraparound

What's different about CVE-2026-33611?

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.

The technical impact and remediation are identical to the primary CVE in the bundle. The same vendor patch closes both.

How to fix CVE-2026-33611

Apply the patched build per the primary write-up: How to Fix CVE-2026-33608.

The patch installation procedure, verification commands, and interim mitigations are documented there. Reusing one runbook keeps the rollout consistent across the bundle.

Frequently asked questions

Is CVE-2026-33611 fixed by the same patch as CVE-2026-33608?

Yes. CVE-2026-33611 ships in the same vendor advisory as CVE-2026-33608. Applying the patched build named in the primary write-up closes both.

What is the CVSS score for CVE-2026-33611?

The CVSS base score is 6.5 (Medium).

Is it being exploited?

It is not currently listed in CISA KEV.

References


*Part of the Authoritative bundle. Full procedure at CVE-2026-33608.*