CVE-2016-9158
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- No fix version is held. The CNA's first reference is the place to look: securityfocus.com
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
A vulnerability has been identified in SIMATIC S7-300 CPU family (All versions), SIMATIC S7-300 CPU family (incl. related ET200 CPUs and SIPLUS variants) (All versions), SIMATIC S7-400 PN/DP V6 and below CPU family (incl. SIPLUS variants) (All versions), SIMATIC S7-400 PN/DP V7 CPU family (incl. SIPLUS variants) (All versions), SIMATIC S7-400 V6 and earlier CPU family (All versions), SIMATIC S7-400 V7 CPU family (All versions). Specially crafted packets sent to port 80/tcp could cause the affected devices to go into defect mode. A cold restart is required to recover the system.
- weakness
- CWE-20: Improper Input Validation
- affected
- Siemens AG SIMATIC S7-300 CPU family; Siemens AG SIMATIC S7-300 CPU family (incl. related ET200 CPUs and SIPLUS variants); Siemens AG SIMATIC S7-400 PN/DP V6 and below CPU family (incl. SIPLUS variants); Siemens AG SIMATIC S7-400 PN/DP V7 CPU family (incl. SIPLUS variants); Siemens AG SIMATIC S7-400 V6 and earlier CPU family; Siemens AG SIMATIC S7-400 V7 CPU family
- versions
- No affected-version range in held sources.
- fixed in
- No fix version in held sources.
- assigned by
- siemens
- published
- 2016-12-17
check us securityfocus.com securitytracker.com ics-cert.us-cert.gov siemens.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 4 Feb 2022 | 0.01018 | |
| 7 Mar 2023 | 0.00373 | scoring model v2023.03.01 |
| 17 Mar 2025 | 0.01146 | scoring model v2025.03.14 |
| 29 Mar 2025 | 0.02173 | |
| 30 Mar 2025 | 0.01146 | |
| 15 Jun 2026 | 0.03002 | scoring model v2026.06.15 |
| 27 Jul 2026 | 0.03027 | |
| 23 Aug 2026 | 0.03036 | |
| 30 Aug 2026 | 0.03027 | |
| 5 Sep 2026 | 0.03036 | |
| 6 Sep 2026 | 0.03027 |
11 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.03 on 2026-09-06 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- No fix version is held. One published by the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2016-9158', '2026-11-01T23:59:59.999999Z', now());