CVE-2022-46346
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.264; parasolid 34.0.252; parasolid 34.1.242; parasolid 35.0.170 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.264), Parasolid V34.0 (All versions < V34.0.252), Parasolid V34.1 (All versions < V34.1.242), Parasolid V35.0 (All versions < V35.0.170), Solid Edge SE2022 (All versions < V222.0MP12), Solid Edge SE2022 (All versions), Solid Edge SE2023 (All versions < V223.0Update2). The affected applications contain an out of bounds write past the end of an allocated structure while parsing specially crafted X_B files. This could allow an attacker to execute code in the context of the current process. (ZDI-CAN-19071)
- weakness
- CWE-787: Out-of-bounds Write
- affected
- Siemens Parasolid V33.1; Siemens Parasolid V34.0; Siemens Parasolid V34.1; Siemens Parasolid V35.0; Siemens Solid Edge SE2022; Siemens Solid Edge SE2023
- published ranges
- siemens parasolid >= 33.1 < 33.1.264; siemens parasolid >= 34.0 < 34.0.252; siemens parasolid >= 34.1 < 34.1.242; siemens parasolid >= 35.0 < 35.0.170; and 1 more on the CVE page
- first unaffected version, by branch
- parasolid 33.1.264; parasolid 34.0.252; parasolid 34.1.242; parasolid 35.0.170
- 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
- 2022-12-13
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 Dec 2022 | 0.02155 | |
| 16 Dec 2022 | 0.01036 | |
| 15 Feb 2023 | 0.01005 | |
| 7 Mar 2023 | 0.00075 | scoring model v2023.03.01 |
| 17 Mar 2025 | 0.00071 | scoring model v2025.03.14 |
| 18 Feb 2026 | 0.00112 | |
| 28 Feb 2026 | 0.00054 | |
| 15 Jun 2026 | 0.00324 | scoring model v2026.06.15 |
| 28 Sep 2026 | 0.00338 |
24 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-28 (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.264; parasolid 34.0.252; parasolid 34.1.242; parasolid 35.0.170. 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-46346', '2026-11-01T23:59:59.999999Z', now());