Skip to content
Fencer Vulns
high 7.8

CVE-2023-25003 json

A maliciously crafted pskernel.dll file in Autodesk AutoCAD 2023 and Maya 2022 may be used to trigger out-of-bound read write / read vulner…

published 2023-06-23 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-28985

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 16%
public exploits
0
none known

Summary

A maliciously crafted pskernel.dll file in Autodesk AutoCAD 2023 and Maya 2022 may be used to trigger out-of-bound read write / read vulnerabilities. Exploitation of this vulnerability may lead to code execution.

Patch / fix

  • autodesk alias 2023.1.1
  • autodesk autocad 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk autocad_advance_steel 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk autocad_architecture 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk autocad_civil_3d 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk autocad_electrical 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk autocad_lt 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk autocad_map_3d 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk autocad_mechanical 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk autocad_mep 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk autocad_plant_3d 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1
  • autodesk infraworks 2021.2, 2022.1, 2023.1
  • autodesk inventor 2021.5, 2022.4, 2023.3.1
  • autodesk maya_usd 2022.5, 2023.3
  • autodesk navisworks 2022.4, 2023.2
  • autodesk revit 2021.1.8
  • autodesk vred 2023.4

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
23 mo ago

Exploit prediction

0.25% chance of exploitation in the next 30 days, higher than 16% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • n/a AutoCAD, Maya

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.