CVE-2026-42002

Race Condition in Powerdns Authoritative 4.7.0 – 4.9.15

Race Condition

Published

21 May 2026

Modified

23 July 2026

CVSS Score v3.1 5.9

Click a component to see what it means

Raw vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS Score 0.0026 18th percentile

Risk Priority 45 floored blend · peak EPSS

Summary

CVE-2026-42002 is a medium-severity Signal Handler Race Condition (CWE-364) vulnerability in Powerdns Authoritative. Its CVSS base score is 5.9 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

🇪🇺 ENISA EUVD: EUVD-2026-31260

Vulnerability Data

Concurrency and locking defects in GSS-TSIG

CWE(s): CWE-364

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.

attack.mitre.org →

Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-33611Same product: Powerdns Authoritative

CVE-2026-42000Same product: Powerdns Authoritative

CVE-2026-33608Same product: Powerdns Authoritative

CVE-2026-42396Same product: Powerdns Authoritative

CVE-2026-41999Same product: Powerdns Authoritative

CVE-2026-33609Same product: Powerdns Authoritative

CVE-2026-42001Same product: Powerdns Authoritative

CVE-2026-33610Same product: Powerdns Authoritative

CVE-2026-33257Same product: Powerdns Authoritative

CVE-2026-33260Same product: Powerdns Authoritative

Affected Assets

powerdns

authoritative

4.7.0 — 4.9.15 · 5.0.0 — 5.0.5

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including concurrency and fuzz testing) can discover signal-handler race conditions before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles such as least privilege, complete mediation, and avoidance of shared mutable state in handlers directly reduce introduction of signal-handler race conditions.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match

prevents

Secure SDLC practices directly prevent introduction of signal-handler race conditions during coding and review.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match

finds

Security testing can detect signal-handler race conditions before release.

A.8.25 Secure development life cycle partial match

prevents

Secure SDLC practices can require avoidance of unsafe signal handling patterns.

A.8.27 Secure system architecture and engineering principles partial match

degrades

Secure architecture principles can mandate safe concurrency and signal design.

A.8.28 Secure coding partial match

prevents

Secure coding standards directly prohibit race-prone signal handlers.