CVE-2026-42001: Insufficient Validation of Autoprimary SOA Queries
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: PowerDNS Authoritative 4.9.15, 5.0.5.
Low priority for now. Upgrade to PowerDNS Authoritative 4.9.15, 5.0.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
- Published
- May 21, 2026
- Updated
- Jul 23, 2026
- EPSS
- 0.3% · 30th percentile
- CWE
- CWE-400
Report tools
Action score
30
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · OX
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| powerdns | authoritative | cpe:2.3:a:powerdns:authoritative |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (OX). Independent of NVD's CPE analysis and usually ahead of it.
PowerDNS Authoritative
- 4.9.0 and later · before 4.9.15affected · semver
- 5.0.0 and later · before 5.0.5affected · semver
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- powerdns authoritative4.1.0 and later · before 4.9.15
- powerdns authoritative5.0.0 and later · before 5.0.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.23 | pdns | before 5.0.5-r0 | 5.0.5-r0 |
| Debian:12 | pdns | from 0 | — |
| Debian:13 | pdns | before 4.9.15-0+deb13u1 | 4.9.15-0+deb13u1 |
| Debian:14 | pdns | before 5.0.5-1 | 5.0.5-1 |
Same product
powerdns: all recordsOther highest-scoring records for the same primary product.
- CVE-2015-1868The label decompression functionality in PowerDNS Recursor 3.5.x, 3.6.x before 3.6.3, and 3.7.x before 3.7.2 and Authoritative (Auth)…55Plan
- CVE-2016-5427PowerDNS (aka pdns) Authoritative Server before 3.4.10 does not properly handle a .49Plan
- CVE-2020-24698An issue was discovered in PowerDNS Authoritative through 4.3.0 when --enable-experimental-gss-tsig is used.40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-41999May 21, 2026 · Incorrect Behaviour of Views with TCP PROXY Requests19Monitor
- ← EarlierCVE-2026-42000May 21, 2026 · Insufficient Validation of Names During AXFR34Monitor
- Later →CVE-2026-42002May 21, 2026 · Concurrency and locking defects in GSS-TSIG30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PowerDNS Authoritative | 4.9.15 | Vendor (CNA) |
| PowerDNS Authoritative | 5.0.5 | Vendor (CNA) |
| alpine:pdns | 5.0.5-r0 · Alpine:v3.23 | Package registry (OSV) |
| debian:pdns | 4.9.15-0+deb13u1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- lazarux0x1337finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-3361029 days apartPossible file descriptor exhaustion in forward-dnsupdate30Monitor
- CVE-2026-4200535 days apartInsufficient input validation of internal web server17Monitor
Not on record for this CVE: EPSS history · patch commit or PR link · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-secondary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.