CVE-2022-39145
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 the fixed version for your release line, or later: parasolid 33.1.263; parasolid 34.0.252; parasolid 34.1.242; parasolid 35.0.164; simcenter femap 2022.1.3; simcenter femap 2022.2.2 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 Parasolid V33.1 (All versions < V33.1.262), Parasolid V33.1 (All versions >= V33.1.262 < V33.1.263), Parasolid V34.0 (All versions < V34.0.252), Parasolid V34.1 (All versions < V34.1.242), Parasolid V35.0 (All versions < V35.0.161), Parasolid V35.0 (All versions >= V35.0.161 < V35.0.164), Simcenter Femap V2022.1 (All versions < V2022.1.3), Simcenter Femap V2022.2 (All versions < V2022.2.2). The affected application is vulnerable to out of bounds read past the end of an allocated buffer when parsing X_T files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-17496)
- weakness
- CWE-125: Out-of-bounds Read
- affected
- Siemens Parasolid V33.1; Siemens Parasolid V34.0; Siemens Parasolid V34.1; Siemens Parasolid V35.0; Siemens Simcenter Femap V2022.1; Siemens Simcenter Femap V2022.2
- published ranges
- siemens simcenter femap >= 2022.1 < 2022.1.3; siemens simcenter femap >= 2022.2 < 2022.2.2; siemens parasolid >= 33.1 < 33.1.263; siemens parasolid >= 34.0 < 34.0.252; and 2 more on the CVE page
- first unaffected version, by branch
- parasolid 33.1.263; parasolid 34.0.252; parasolid 34.1.242; parasolid 35.0.164; simcenter femap 2022.1.3; simcenter femap 2022.2.2
- assigned by
- siemens
- published
- 2022-09-13
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 |
|---|---|---|
| 14 Sep 2022 | 0.02155 | |
| 15 Sep 2022 | 0.01036 | |
| 7 Mar 2023 | 0.0005 | scoring model v2023.03.01 |
| 8 Mar 2023 | 0.0005 | |
| 17 Mar 2025 | 0.00166 | scoring model v2025.03.14 |
| 15 Jun 2026 | 0.00232 | scoring model v2026.06.15 |
| 24 Jun 2026 | 0.00241 | |
| 19 Aug 2026 | 0.00243 | |
| 10 Sep 2026 | 0.00255 |
19 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-09-10 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: parasolid 33.1.263; parasolid 34.0.252; parasolid 34.1.242; parasolid 35.0.164; simcenter femap 2022.1.3; simcenter femap 2022.2.2. 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-2022-39145', '2026-10-30T23:59:59.999999Z', now());