OnlyDNS core infrastructure, global Anycast authoritative nameservers, database clusters, and API backends are not impacted. Our developer tools (@onlydns/cli, @onlydns/mcp, and @onlydns/sdk) have been audited and verified with up-to-date, vulnerability-free dependencies. We encourage developers to upgrade their host Node.js runtimes.
The Node.js project has published scheduled security updates for all active release lines (details available in the official Node.js November 2026 Security Releases announcement). These upstream releases resolve vulnerabilities across active Current and Long Term Support (LTS) branches within the core runtime and its bundled dependencies.
Because modern developer workflows frequently run our command-line tools (@onlydns/cli), AI agent integrations (@onlydns/mcp), and JavaScript/TypeScript client libraries (@onlydns/sdk) in Node.js-powered development workstations, CI/CD runners, and Docker containers, we are sharing this advisory as part of our routine operational hygiene practices.
Status of OnlyDNS Platform & Developer Tools
We have reviewed the upstream disclosures and completed security audits across our ecosystem:
Not Affected. Our 23-node global Anycast network, PowerDNS core, dnsdist edge ingress, database clusters, and API backend services operate on hardened Linux environments independent of the affected Node.js runtime layers.
Audited & Clean. We conducted thorough dependency tree checks and automated vulnerability scans across @onlydns/cli, @onlydns/mcp, and @onlydns/sdk. All dependencies are up to date with zero known security advisories.
Recommended Action: Updating Your Node.js Environments
Because developer tools execute within your local machine, continuous integration workflows, or container hosts, keeping your underlying Node.js runtime current is standard security best practice. We recommend upgrading your active Node.js installations to the latest maintenance release for your version branch.
1. Check Your Current Node.js Version
Inspect the runtime version active in your terminal:
node --version
2. Upgrade via Your Version Manager
Depending on how you manage Node.js versions on your workstation:
# Install and switch to the latest LTS release
nvm install --lts
nvm use --lts
fnm install --lts
fnm use lts-latest
brew update && brew upgrade node
3. Update CI/CD Runners & Docker Base Images
If you run OnlyDNS CLI automation or custom scripts in CI/CD pipelines (such as GitHub Actions, GitLab CI, or Jenkins) or within containerized environments, update your base image references to the latest patched tags (e.g., node:22-alpine or node:20-slim).
Verifying OnlyDNS Developer Tooling
Once your runtime environment is updated, you can verify your OnlyDNS developer tools are current:
npx @onlydns/cli --version# Or update your global CLI installation if installed globally
npm install -g @onlydns/cli@latest# Check MCP server version
npx @onlydns/mcp --version
Developer Tooling Ecosystem
- OnlyDNS CLI (@onlydns/cli): Terminal-based DNS record management, zone imports, and JSON output for automated scripting.
- OnlyDNS MCP Server (@onlydns/mcp): Official Model Context Protocol integration for Claude Desktop, Cursor, and autonomous AI agents.
- Official OnlyDNS SDKs: Type-safe client libraries for TypeScript/JavaScript, Python, Go, and PHP.
If you have questions regarding this advisory or integrating OnlyDNS tools into your development workflows, please reach out via our support portal or community channels.