Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Active exploitation is not confirmed from current sources for CVE-2026-81861. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

No. CVE-2026-81861 is not listed in CISA KEV in the supplied enrichment data. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

1 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-81861 using CVSS 5.9, EPSS 0%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Prioritize based on EPSS, PoC availability, and external exposure. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

mediumCredentialspublic exploit

CVE-2026-81861

CVE-2026-81861 — CWE-522: Insufficiently Protected Credentials vulnerability that could result in exposure of authentication information and unauthorized…

CWE-522: Insufficiently Protected Credentials vulnerability that could result in exposure of authentication information and unauthorized access to RTU functionality.

Published Sep 11, 2026Updated Sep 11, 2026Sources: NVD, Schneider Electric (CNA), GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Exploit code

public exploit, none observed

EPSS

ahead of 0% of scored CVEs

Affects

Schneider Electric

7 products listed

CVSS base

5.9

medium

Remediation

The vendor's own words where we have them.

Upgrade SCADAPack 47x to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Prioritize based on EPSS, PoC availability, and external exposure.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
Schneider Electric	SCADAPack 47x	All versions	Vulnerable
Schneider Electric	SCADAPack 47xi	All versions	Vulnerable
Schneider Electric	SCADAPack 47xd	All versions	Vulnerable
Schneider Electric	SCADAPack 470R	All versions	Vulnerable
Schneider Electric	SCADAPack 57x	All versions	Vulnerable
Schneider Electric	SCADAPack 3xx	All versions	Vulnerable
Schneider Electric	SCADAPack 32	All versions	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
5.9	CVSS 4.0	medium	—	—	Schneider Electric (CNA)

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-522 · Insufficiently Protected Credentials

Gain Privileges or Assume Identity

Mitigation: Use an appropriate security mechanism to protect the credentials.

Weakness & attack patterns

CWE-522

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-653 · Use of Known Windows CredentialsCAPEC-555 · Remote Services with Stolen CredentialsCAPEC-644 · Use of Captured Hashes (Pass The Hash)CAPEC-509 · KerberoastingCAPEC-474 · Signature Spoofing by Key TheftCAPEC-561 · Windows Admin Shares with Stolen CredentialsCAPEC-551 · Modify Existing ServiceCAPEC-652 · Use of Known Kerberos CredentialsCAPEC-645 · Use of Captured Tickets (Pass The Ticket)CAPEC-50 · Password Recovery ExploitationCAPEC-560 · Use of Known Domain CredentialsCAPEC-600 · Credential Stuffing

T1552.004Unsecured Credentials: Private Keys
T1558.003Steal or Forge Kerberos Tickets: Kerberoasting
T1543Create or Modify System Process

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable SCADAPack 47x, SCADAPack 47xi, SCADAPack 47xd, SCADAPack 470R, SCADAPack 57x, SCADAPack 3xx, SCADAPack 32.
Monitor for scanner or exploit-pattern traffic after 1 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 5.9 (AV:N)
Sep 11, 2026 · NVD
Initial · CVE published
Sep 11, 2026 · NVD
CVE published by MITRE.
Sep 11, 2026 · SOCRadar CTI

References

1 on the record

download.se.com/files?p_Doc_Ref=SEVD-2026-251-03&p_enDocType=Security+and+Safety+Notice&p_File_Name=SEVD-2026-251-03.pdf
Vendor Advisory

Elsewhere on this site

Schneider Electricevery CVE for this vendor
Credentialssame class
CWE-522other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-81861 is CWE-522: Insufficiently Protected Credentials vulnerability that could result in exposure of authentication information and unauthorized…, a medium vulnerability affecting SCADAPack 47x, SCADAPack 47xi, SCADAPack 47xd, SCADAPack 470R, SCADAPack 57x, SCADAPack 3xx, SCADAPack 32 from Schneider Electric. The current evidence does not list it in CISA KEV, and the exploit status is: Active exploitation is not confirmed from current sources for CVE-2026-81861. Public exploit evidence is: 1 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 5.9 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.