How severe is CVE-2016-8562?

CVE-2016-8562 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2016-8562?

CVE-2016-8562 affects the following products: siemens simatic cp 1543-1 firmware, siemens siplus net cp 1543-1 firmware.

How do I patch CVE-2016-8562?

Apply the siemens simatic cp 1543-1 firmware security patch or hotfix for CVE-2016-8562 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2016-8562 across my infrastructure?

Inventory every siemens simatic cp 1543-1 firmware deployment and check each version against the affected-products list above.

How do I mitigate CVE-2016-8562 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2016-8562 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2016-8562, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2016-8562?

CVE-2016-8562 has an EPSS (Exploit Prediction Scoring System) score of 3.6%, placing it in the 89th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2016-8562 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2016-8562 (Siemens SIMATIC CP 1543-1 Improper Privilege Management Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-03-24. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2016-8562?

CVE-2016-8562 affects siemens simatic cp 1543-1 firmware; siemens siplus net cp 1543-1 firmware. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2016-8562 published, and has it been updated?

CVE-2016-8562 was published on November 18, 2016 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2016-8562 — Simatic Cp 1543-1 Firmware

HIGH

CVE-2016-8562 is a high-severity (CVSS 7.5) vulnerability in siemens simatic cp 1543-1 firmware. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-03-03) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.

A vulnerability has been identified in SIMATIC CP 1543-1 (All versions < V2.0.28), SIPLUS NET CP 1543-1 (All versions < V2.0.28). Under special conditions it was possible to write SNMP…

Published

Nov 18, 2016

Updated

Jun 17, 2026

Affected

2 products

Patched

See advisory

Exploits

1 known

Exploitation data as of Oct 22, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-03-03. Federal agencies were required to remediate by 2022-03-24.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2016-8562.

EPSS Exploitation Probability

via FIRST.org ↗

3.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs89th percentile — riskier than 89% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2016-8562 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

A vulnerability has been identified in SIMATIC CP 1543-1 (All versions < V2.0.28), SIPLUS NET CP 1543-1 (All versions < V2.0.28). Under special conditions it was possible to write SNMP variables on port 161/udp which should be read-only and should only be configured with TIA-Portal. A write to these variables could reduce the availability or cause a denial-of-service.

Affected Products

2 products · 2 configurations

simatic cp 1543-1 firmwaresiemens

< 2.0.28

range

siplus net cp 1543-1 firmwaresiemens

< 2.0.28

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

A vulnerability has been identified in SIMATIC CP 1543-1 (All versions <…

cisa.govCISAMar 2022

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every siemens simatic cp 1543-1 firmware deployment and check each version against the affected-products list above.
Fix
Apply the siemens simatic cp 1543-1 firmware security patch or hotfix for CVE-2016-8562 on the affected version, following the vendor advisory for your exact build.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2016-8562 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works