CVE-2023-49128
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
- Upgrade to solid edge se2023 223.0 or later upper bounds of the CVE record's affected ranges
- 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 Solid Edge SE2023 (All versions < V223.0 Update 10). The affected application contains an out of bounds write past the end of an allocated buffer while parsing a specially crafted PAR file. This could allow an attacker to execute code in the context of the current process.
- weakness
- CWE-787: Out-of-bounds Write
- affected
- Siemens Solid Edge SE2023
- published ranges
- siemens solid edge se2023 < 223.0; siemens solid edge se2023 223.0; siemens solid edge se2023 223.0-update_0001; siemens solid edge se2023 223.0-update_0002; and 7 more on the CVE page
- first unaffected version, by branch
- solid edge se2023 223.0
- severity
- 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
- assigned by
- siemens
- published
- 2024-01-09
check us cert-portal.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 |
|---|---|---|
| 10 Jan 2024 | 0.00064 | |
| 11 Jan 2024 | 0.00066 | |
| 18 Feb 2024 | 0.00053 | |
| 23 Mar 2024 | 0.0005 | |
| 10 Feb 2025 | 0.00051 | |
| 17 Mar 2025 | 0.00053 | scoring model v2025.03.14 |
| 25 Mar 2025 | 0.00057 | |
| 29 Mar 2025 | 0.0011 | |
| 30 Mar 2025 | 0.00057 | |
| 15 Apr 2025 | 0.00093 | |
| 30 May 2025 | 0.00127 | |
| 18 Nov 2025 | 0.00057 | |
| 21 Nov 2025 | 0.00127 | |
| 15 Jun 2026 | 0.00201 | scoring model v2026.06.15 |
14 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.00 on 2026-06-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: solid edge se2023 223.0. A newer fix from 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-2023-49128', '2026-11-01T23:59:59.999999Z', now());