basicsecurity.net
Proof, not just disclosure.
Threats / Rockwell / CVE-2021-22681
CVE-2021-22681 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Rockwell Multiple Products vulnerability

Multiple Rockwell Automation products contain insufficient credential protection allowing discovery of verification keys used by Logix controllers. Exploitation enables unauthorized applications to connect to controllers with network access

Verdict

Today item — known-exploited.

An attacker with network access to a Logix controller can discover insufficiently protected credentials to impersonate legitimate design software and establish unauthorized connections, potentially compromising industrial control system integrity.

CISA KEV Yes · 2026-03-053EPSS 0.25455 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-03-05).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.25455 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Rockwell, Multiple Products. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-522 Insufficiently Protected Credentials — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I discover the verification key used by Logix controllers through insufficient protection mechanisms in Studio 5000 Logix Designer.
Business
Attackers gain the ability to forge legitimate communications with critical industrial control infrastructure.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I use the discovered key to create an unauthorized application that mimics legitimate Rockwell design software.
Business
The organization loses the ability to distinguish between authorized and malicious controller communications.
3

Lateral reach — past segmentation narrative 3

Attacker
I connect my unauthorized application to Logix controllers on the network, establishing a foothold for further compromise.
Business
Operational technology systems face direct compromise risk, potentially enabling manipulation of industrial processes.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 4 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by icscert (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by icscertCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.