ManageEngine says a user authorized to manage a Windows-backed DNS zone could supply an unsafe TXT record value.During DNS record operations, DDI Central could pass that value into PowerShell without sufficient validation. Commands could then run on the managed Windows DNS server under the account configured for DDI Central DNS management.
What it allows
How Could CVE-2026-19421 Reach a Windows DNS Server?
ManageEngine says DDI Central incorporated user-supplied TXT record values into PowerShell commands for managed Windows DNS operations. The missing input validation created a path from a permitted DNS record change to command execution on that Windows server.
An attacker would first need an authenticated account with permission to manage a Windows-backed DNS zone. If the unsafe value were processed, commands could run with the privileges of DDI Central's configured Windows DNS management account. This is the vendor's stated potential impact, not a confirmed attack.
The related CVE-2026-19422 authentication bypass concerns unauthenticated Windows agent synchronization. Its precondition and DNS or DHCP data impact differ from this TXT record injection, although ManageEngine names build 6301 as the fix for both.
Brandefense Blackhole counted one dark-chat post matching CVE-2026-19421 from August 14 through November 12, 2026. This measures discussion in that source and period; it does not establish an incident or active exploitation.
CVE-2026-19421 was absent from CISA KEV catalog version 2026.11.10. That snapshot predates NVD's November 12 publication, so the operational exploitation status remains unknown. Use a vulnerability intelligence platform to prioritize the affected inventory.
Who is affected
Which Builds and DNS Operations Need CVE-2026-19421 Review?
ManageEngine names DDI Central 6.3.0, build 6300, as affected and build 6301 as fixed. NVD describes versions below build 6301 as affected; its record has not yet analyzed product configurations.
The relevant workflow manages TXT records on a Windows-backed DNS zone. Inventory DDI Central Consoles, the Windows DNS servers they manage, and the applicable Windows DDI management components. An external attack surface management inventory can help prioritize exposed deployments.
ManageEngine directs customers to update the Console and applicable Windows DDI management components to build 6301 or later with the corresponding service pack. Check the running build and component versions after maintenance rather than relying only on the service pack download.
Timeline
-
2026-08-18
ManageEngine says it fixed CVE-2026-19421 in DDI Central build 6301.
-
2026-11-12
NVD published the CVE record and listed CVSS 3.1 8.8 High.
What to do
-
Find affected DDI Central deployments
Identify DDI Central build 6300 and any lower builds. Record managed Windows DNS servers, Windows-backed zones, and accounts permitted to change their TXT records.
-
Apply the build 6301 service pack
Update the DDI Central Console and applicable Windows DDI management components to build 6301 or later, following ManageEngine's service pack guidance.
-
Verify the installed versions
After maintenance, confirm the running Console build and each applicable Windows DDI management component. Keep the version evidence with the change record.
-
Review privileged DNS changes
As a Brandefense defensive recommendation, review recent TXT record changes and Windows DNS management activity for unexplained commands or changes. Preserve relevant logs if investigation is needed.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-19421 in Brandefense Atlas
The Atlas record of CVE-2026-19421: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What access does CVE-2026-19421 require?
ManageEngine says the attacker must be authenticated and permitted to manage a Windows-backed DNS zone. The flaw is in TXT record processing, not an unauthenticated request path.
Which build fixes CVE-2026-19421?
ManageEngine lists build 6301 as fixed. Install the corresponding service pack on the Console and applicable Windows DDI management components, then verify their running versions.
Where could injected commands run?
ManageEngine says they could run on the managed Windows DNS server under the Windows account configured for DDI Central DNS management.
How does CVE-2026-19421 differ from CVE-2026-19422?
CVE-2026-19421 needs an authorized DNS zone user and involves TXT record handling. CVE-2026-19422 is an unauthenticated Windows DNS and DHCP agent synchronization bypass.
Sources
- DDI Central Security Update CVE-2026-19421ManageEngine
- CVE-2026-19421 DetailNational Vulnerability Database
- DDI Central Security Update CVE-2026-19422ManageEngine
- Known Exploited Vulnerabilities CatalogCISA