CVE-2026-129468: dnsmgr: missing authz exposes Cloudflare domain DNS lines

MEDIUM
Published November 15, 2026
CISO Take

CVE-2026-129468 is a missing authorization flaw (CWE-862) in the Netcccyun dnsmgr DNS management panel, versions 2.18 up to 2.22. Any restricted sub-user can iterate the domain_id parameter on POST /cloudflare/get_domain_default_line and read DNS line lists and default lines for domains they were never granted. The impact is limited to low-confidentiality disclosure (CVSS 4.3, no integrity or availability impact), and there is no KEV listing, no public exploit, no Nuclei template and no EPSS score yet, so urgency is low. This is a DNS management tool, not a core AI/ML component, so AI exposure is only indirect: it matters if it manages DNS for AI endpoints or ML UIs. Upgrade to 2.22 or later, and review whether sub-users or tenants share a panel with domains of differing sensitivity.

Sources:NVDVulnCheckGitHub

What is the risk?

Low-to-medium risk. The attack is network-reachable, low complexity, needs only low privileges (an existing restricted account) and no user interaction. Impact is confined to confidentiality of DNS line metadata and domain ID enumeration. No exploit code, KEV listing or EPSS data suggests active exploitation. The tool is tangential to AI/ML, so AI-specific risk is indirect.

How does the attack unfold?

Initial Access
Attacker logs in to dnsmgr with a restricted sub-user or single-domain account.
AML.T0012
Enumeration
Attacker iterates domain_id in POST /cloudflare/get_domain_default_line to discover domains outside their permissions.
AML.T0006
Impact
DNS line lists and default lines of other tenants' domains are disclosed, exposing infrastructure details.

How severe is it?

CVSS 3.1
4.3 / 10
EPSS
0.2%
chance of exploitation in 30 days
Higher than 10% of all CVEs
Exploitation Status
No known exploitation
Sophistication
Trivial

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACLow
PRLow
UINone
SUnchanged
CLow
INone
ANone

What should I do?

1 step
  1. 1) Upgrade netcccyun dnsmgr to version 2.22 or later (fix commit 175468c). 2) Until patched, remove or limit restricted sub-user and single-domain accounts, or restrict panel access to trusted networks or a VPN. 3) Audit web logs for repeated POST requests to /cloudflare/get_domain_default_line with sequential domain_id values from low-privilege sessions. 4) Review which AI/ML-related domains are managed in the panel and rotate any exposed operational detail if needed. 5) Apply authorization checks on all object-level endpoints as a regression test.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001
A.6.2.6-AI system operation and monitoring
NIST AI RMF
GOVERN 6.1-Policies for third-party software and supply chain risks

Frequently Asked Questions

What is CVE-2026-129468?

CVE-2026-129468 is a missing authorization flaw (CWE-862) in the Netcccyun dnsmgr DNS management panel, versions 2.18 up to 2.22. Any restricted sub-user can iterate the domain_id parameter on POST /cloudflare/get_domain_default_line and read DNS line lists and default lines for domains they were never granted. The impact is limited to low-confidentiality disclosure (CVSS 4.3, no integrity or availability impact), and there is no KEV listing, no public exploit, no Nuclei template and no EPSS score yet, so urgency is low. This is a DNS management tool, not a core AI/ML component, so AI exposure is only indirect: it matters if it manages DNS for AI endpoints or ML UIs. Upgrade to 2.22 or later, and review whether sub-users or tenants share a panel with domains of differing sensitivity.

Is CVE-2026-129468 actively exploited?

No confirmed active exploitation of CVE-2026-129468 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-129468?

1) Upgrade netcccyun dnsmgr to version 2.22 or later (fix commit 175468c). 2) Until patched, remove or limit restricted sub-user and single-domain accounts, or restrict panel access to trusted networks or a VPN. 3) Audit web logs for repeated POST requests to /cloudflare/get_domain_default_line with sequential domain_id values from low-privilege sessions. 4) Review which AI/ML-related domains are managed in the panel and rotate any exposed operational detail if needed. 5) Apply authorization checks on all object-level endpoints as a regression test.

What systems are affected by CVE-2026-129468?

This vulnerability affects the following AI/ML architecture patterns: DNS management panels, Multi-tenant admin UIs, Model serving endpoint infrastructure (indirect).

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

CVE-2026-129468 has a CVSS v3.1 base score of 4.3 (MEDIUM). The EPSS exploitation probability is 0.20%.

What is the AI security impact?

Affected AI Architectures

DNS management panelsMulti-tenant admin UIsModel serving endpoint infrastructure (indirect)

MITRE ATLAS Techniques

AML.T0006Active Scanning
AML.T0012Valid Accounts

Compliance Controls Affected

ISO 42001: A.6.2.6
NIST AI RMF: GOVERN 6.1

What are the technical details?

Original Advisory

Netcccyun dnsmgr 2.18 before 2.22 contains a missing authorization vulnerability in POST /cloudflare/get_domain_default_line that allows restricted users to access domains outside their permissions. Restricted sub-users or single-domain logins can iterate the domain_id parameter to enumerate panel domain ids and read each domain's DNS line list and default line.

Exploitation Scenario

An attacker or malicious tenant holding a restricted sub-user login to a shared dnsmgr panel scripts requests to POST /cloudflare/get_domain_default_line, incrementing domain_id. For each valid ID, the panel returns the DNS line list and default line of domains belonging to other tenants, including those fronting AI inference APIs or ML dashboards. The attacker builds an inventory of the organization's AI-related domains and their routing configuration, then uses it to target those endpoints in follow-on reconnaissance.

Weaknesses (CWE)

CWE-862 — Missing Authorization: The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

  • [Architecture and Design] Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • [Architecture and Design] Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].

Source: MITRE CWE corpus.

CVSS Vector

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

Timeline

Published
November 15, 2026
Last Modified
November 16, 2026
First Seen
November 15, 2026

Related Vulnerabilities