CVE-2022-41306

CVE-2022-41306 is a high-severity vulnerability in Autodesk Design Review with a CVSS 3.x base score of 7.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-787.

Key facts

Description

A maliciously crafted PCT file when consumed through DesignReview.exe application could lead to memory corruption vulnerability by write access violation. This vulnerability in conjunction with other vulnerabilities could lead to code execution in the context of the current process.

Frequently asked questions

What is CVE-2022-41306?
A maliciously crafted PCT file when consumed through DesignReview.exe application could lead to memory corruption vulnerability by write access violation. This vulnerability in conjunction with other vulnerabilities could lead to code execution in the context of the current process.
How severe is CVE-2022-41306?
CVE-2022-41306 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-41306 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (32nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-41306?
CVE-2022-41306 affects Autodesk Design Review. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-41306?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2022-41306 published?
CVE-2022-41306 was published on 2022-10-14 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Autodesk Design Review

All CVEs affecting Autodesk Design Review →

Other CWE-787 (Out-of-bounds Write) vulnerabilities

Browse all CWE-787 (Out-of-bounds Write) vulnerabilities →