PowerDNS Authoritative up to 5.0.4 Proxy Request access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in PowerDNS Authoritative up to 5.0.4. It has been declared as problematic. This impacts an unknown function of the component Proxy Request Handler. Such manipulation leads to Remote Code Execution. This vulnerability is referenced as CVE-2026-41999. It is possible to launch the attack remotely. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in PowerDNS Authoritative up to 5.0.4 and classified as problematic. Affected by this issue is some unknown processing of the component Proxy Request Handler. The manipulation with an unknown input leads to a remote code execution vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability.
The weakness was published by Zwique. The advisory is shared for download at docs.powerdns.com. This vulnerability is handled as CVE-2026-41999 since 04/23/2026. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
The vulnerability scanner Nessus provides a plugin with the ID 315771 (Linux Distros Unpatched Vulnerability : CVE-2026-41999), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.0.5 eliminates this vulnerability.
The vulnerability is also documented in the databases at Tenable (315771), EUVD (EUVD-2026-31262) and CERT Bund (WID-SEC-2026-1625). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Affected
- Open Source PowerDNS
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.6
VulDB Temp Score: 5.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.8
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 315771
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-41999
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Authoritative 5.0.5
Timeline
04/23/2026 CVE reserved05/21/2026 Advisory disclosed
05/21/2026 VulDB entry created
05/24/2026 VulDB entry last update
Sources
Advisory: docs.powerdns.comResearcher: Zwique
Status: Confirmed
CVE: CVE-2026-41999 (🔒)
GCVE (CVE): GCVE-0-2026-41999
GCVE (VulDB): GCVE-100-365000
EUVD: 🔒
CERT Bund: WID-SEC-2026-1625 - PowerDNS Authoritative Server: Mehrere Schwachstellen
Entry
Created: 05/21/2026 12:52Updated: 05/24/2026 05:39
Changes: 05/21/2026 12:52 (62), 05/21/2026 15:20 (1), 05/21/2026 18:17 (2), 05/21/2026 18:37 (7), 05/24/2026 05:39 (2)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.