🛡️ CVE-2026-42000 — authoritative

🟡 CVSS 6.8 — Medium ✅ No Known Exploit CWE-77 NVD
6.8
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Insufficient Validation of Names During AXFR

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is changed, meaning a successful attack can affect components beyond the vulnerable one. Rated impact: confidentiality none, integrity high, availability none.

Weakness class

CVE-2026-42000 is classified as CWE-77: Command Injection. User input is placed into a command that the system interprets, allowing extra commands to be appended to the intended one.

Affected software

CVE-2026-42000 is recorded against 2 packages.

  • authoritative (from 5.0.0 up to 5.0.5)
  • unknown

Timeline and source

Published on 21 May 2026 and last revised on 23 July 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

docs.powerdns.com

CVE-2026-42000 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity MEDIUM
CVSS Score 6.8
CVSS Vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
CWE CWE-77
Public Exploit ✅ No
Source NVD
Published 2026-05-21
Updated 2026-08-11
Modified 2026-07-23
Fix URL N/A

Affected Packages

Software From version Fixed in
authoritative 5.0.0 5.0.5
unknown — —

Similar Threats

Vulnerability Monitoring

Track new vulnerabilities in authoritative

CVE-2026-42000 is rated CVSS 6.8 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.

Set Up Free Alerts →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.