CVE-2025-66342 json
A type confusion vulnerability exists in the EMF functionality of Canva Affinity.
published 7mo ago modified 4mo ago also EUVD-2025-208803
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
A type confusion vulnerability exists in the EMF functionality of Canva Affinity. A specially crafted EMF file can trigger this vulnerability, which can lead to memory corruption and result in arbitrary code execution.
Patch / fix
- canva affinity 3.1.0
Is CVE-2025-66342 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 7mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- talosintelligence.com https://talosintelligence.com/vulnerability_reports/TALOS-2025-2297 referenced PoC, tagged "exploit" by a source, unverified
- talosintelligence.com https://www.talosintelligence.com/vulnerability_reports/TALOS-2025-2297 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 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
- Canva Affinity
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
-
talosintelligence.com
/vulnerability_reports/TALOS-2025-2297
exploit, third-party-advisory
-
talosintelligence.com
/vulnerability_reports/TALOS-2025-2297
exploit, third-party-advisory
-
trust.canva.com
/?tcuUid=1f728b0d-17f3-4c9c-97e9-6662b769eb62
vendor-advisory
Sources
- CVE List CVE-2025-66342
- NVD CVE-2025-66342
Fencer Intel 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.