CVE-2021-26726
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA remote code execution vulnerability affecting a Valmet DNA service listening on TCP port 1517, allows an attacker to execute commands with SYSTEM privileges This issue affects: Valmet DNA versions from Collection 2012 until Collection 2021.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA remote code execution vulnerability in the Valmet DNA industrial automation software service listening on TCP port 1517 allows unauthenticated remote attackers to execute arbitrary commands with SYSTEM privileges, achieving full system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 2012, <= 2021CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if TCP port 1517 is listeningRun 'netstat -an | grep 1517' or 'ss -tlnp | grep 1517' on the target system to see if the Valmet DNA service port is open and bound to an interfaceAffected if Port 1517 is found listening on any network interface, especially on interfaces accessible from untrusted networks
-
Identify Valmet DNA installationLook for Valmet DNA installation directories (commonly in C:\Valmet or C:\Program Files\Valmet), check Windows Services for 'Valmet DNA' or 'DNA' named services, or search for executables named 'dna' or related binariesAffected if Valmet DNA software or service is found installed on the system
-
Determine installed Valmet DNA versionCheck the version of the Valmet DNA service executable or service properties: right-click the service in Windows Services > Properties, or check version info on the main DNA executable file properties, or query registry under HKLM\SOFTWARE\Valmet if presentAffected if The installed version falls within the range >= 2012 and <= 2021
-
Verify service is running with elevated privilegesCheck the service logon account in Windows Services - if set to 'Local System' or 'NT AUTHORITY\SYSTEM', the service runs with SYSTEM privileges and the RCE would execute with full system rightsAffected if The Valmet DNA service runs under Local System or an administrator account
The system is affected if TCP port 1517 is exposed on the network, Valmet DNA software version 2012-2021 is installed, and the service runs with SYSTEM-level privileges, allowing unauthenticated remote attackers to achieve full system compromise.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataIsolate the affected Valmet DNA service from untrusted networks via network segmentation and firewall rules restricting access to port 1517; apply vendor patches for affected versions once released.
- Consultation12.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,632.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-26726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-26726 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data